Staging and releasing new M2Eclipse release

Skip to end of metadata
Go to start of metadata
To sign m2eclipse jars with Sonatype certificate, perform these steps from Sonatype release vm


  • if using sonatype release vm...
    • cd m2e-core (or do git clone ssh://<your eclipse commiter username> if no m2e-core)
    • make sure you are on master branch and have no outgoing/incoming changes
    • do git pull
  • set the email and user name for the m2e-core local git repository
      git config <your eclipse commiter email address>
      git config <your name>
  • create release branch
      git branch rb-<version>
  • update master to the next -SNAPSHOT version. from org.eclipse.m2e.parent execute
      mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=<version+1>-SNAPSHOT
      git commit -s -a -m "new version <version+1>-SNAPSHOT"
      git push


  • checkout the release branch
      git checkout rb-<version>
  • pick release BUILDQUALIFIER (eg, 20100924-1107) and update release branch to the release version. From org.eclipse.m2e.parent execute
      mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=<version>.BUILDQUALIFIER
  • edit ../ and change maven-upload-plugin <repositoryPath/> configuration to deploy S-build
  • commit and tag your changes
      git commit -s -a -m "new release <version>.BUILDQUALIFIER"
      git tag <version>.BUILDQUALIFIER
  • stage the release
      mvn clean deploy -Ppublish-site -Dmaven.test.skip=true
  • from nexus gui, find and close staging repo


  • promote nexus staging repo
  • push release tag
      git push origin <version>.BUILDQUALIFIER


  • remove all N builds from Nexus
  • remove release branch if you intend to keep local git repository
      git branch -D rb-<version>
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.