Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

Your Rating: Results: 1 Star2 Star3 Star4 Star5 Star 0 rates

Since we are going to be moving a few modules from the Enterprise Edition into the community space in the future, I thought I'd spare a few sweat drops by sharing a few notes here.

Here's an overview of set of steps to take

  • (star) Create a jira issue, level "critical". Ideally we do this for a major version: makes it easier to find which version is where.
  • (star) Change parent pom (magnolia-parent-pom-enterprise to magnolia-parent-pom-community-module)
  • (star) Change source files license headers
  • (warning) 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:
    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."
    
  • (warning) Think about moving artifacts in Maven repo. (probably not)
  • (star) Fix scm urls in the pom file.
  • (star) Fix Hudson project (scm url, name prefix, permissions)
  • (star) Fix Jira project (category, notifications, permissions)
  • (star) Store ?
  • (star) Docu ?

Simply update local copies with svn switch http://svn.magnolia-cms.com/svn/...new..url...

(star): should be trivial
(warning): pay extra attention. There could be side-effects.

  • No labels