If this is the first time you are cutting a release, please read the How to Build page first.
To build a release you need to change the version qualifier to
v (a local build is tagged with
nightly, if it's build by our Jenkins machine) and sign the plugin (if you have a certificate).
Additionally, for a major or a minor release you need to branch and tag. For a micro release (like 0.1.2), you only need to tag.
In all cases, you need to bump the version number for the branch off which you released (using the tycho-versions-plugin).
delete all locally-built artifacts in your use
.m2 repository (needed until we move to Tycho 0.16.0)
-DlocalArtifacts=ignore to force using the published dependencies
This ensures you are using the IDE bundles that are published in the remote repository, and not mixing with locally built ones.
mvn -Dtycho.localArtifacts=ignore \ -P scala-ide-stable,scala-2.10.x,eclipse-indigo \ -Dversion.tag='v' \ -Djarsigner.storepass=.. \ -Djarsigner.keypass=.. \ -Djarsigner.keystore=/absolute/path/to/typesafe-keystore/typesafe.keystore \ clean package
git push --tags
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=<version+1>-SNAPSHOT
This will increment all versions (in both pom and MANIFEST files) in sync.
git commit -m "Bumped version"and
In addition to the steps for a micro release, you need to create a release branch. Assuming you branch from master, you will do (assuming release
git checkout -b release/0.2.x
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=0.2.1-SNAPSHOT
AND back on master:
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=0.3.0-SNAPSHOT
Last edited by Iulian Dragos,