Page History

...

• Create a jira issue, level "critical". Ideally we do this for a major version: makes it easier to find which version is where.
• Change parent pom (magnolia-parent-pom-enterprise to magnolia-parent-pom-community-module)
• Change source files license headers
• Move the source in the scm. What about tags and branches ? Ideally, they shouldn't move (wrt tooling and licensing) but it might be confusing when browsing the repo. If that's ok, then:

  No Format

  export MODULENAME=imaging # Create new location directories - no trunk svn mkdir http://svn.magnolia-cms.com/svn/community/modules/$MODULENAME \ http://svn.magnolia-cms.com/svn/community/modules/$MODULENAME/branches \ http://svn.magnolia-cms.com/svn/community/modules/$MODULENAME/tags \ -m "Moving $MODULENAME to /community/modules" # Move the trunk: svn mv http://svn.magnolia-cms.com/svn/enterprise/$MODULENAME/trunk \ http://svn.magnolia-cms.com/svn/community/modules/$MODULENAME/ \ -m "Moving $MODULENAME to /community/modules" # Add a README in the /enterprise directory we're leaving behind: svn co http://svn.magnolia-cms.com/svn/enterprise/$MODULENAME/ --depth files && echo "This module was moved to http://svn.magnolia-cms.com/svn/community/modules/$MODULENAME/ Existing branches and tags are kept here for tooling and licensing reasons." > $MODULENAME/README.txt && svn add $MODULENAME/README.txt && svn commit $_ -m "Added README - This module was moved to http://svn.magnolia-cms.com/svn/community/modules/$MODULENAME/ Existing branches and tags are kept here for tooling and licensing reasons."

• Think about moving artifacts in Maven repo. (probably not)
• Fix scm urls in the pom file.
• Fix Hudson project (scm url, name prefix, permissions)
• Fix Jira project (category, notifications, permissions)
• Store ?
• Docu ?

...