-
Notifications
You must be signed in to change notification settings - Fork 70
Deploying
To deploy the project to the snapshot repository you need to modify your settings.xml with the additional fragment (update with your GitHub login name and password):
<profiles>
<profile>
<id>github</id>
<properties>
<github.global.userName>user</github.global.userName>
<github.global.password>password</github.global.password>
</properties>
</profile>
</profiles>
<activeProfiles>
<activeProfile>github</activeProfile>
</activeProfiles>
To deploy the p2 repository to the update site, from the com.*.update site execute:
mvn com.github.github:site-maven-plugin:site
To release a new version execute the following commands:
git checkout -b release-<version>
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=<version>
Check the release passes its test:
mvn clean verify
Then tag the release:
git commit -am "Release <version>"
git tag -a <version> -m "Release <version>"
git push origin master --tags
git branch -d release-<version>
Wait for the master/snapshot CI job to complete, then run:
mvn clean install
cd me.gladwell.eclipse.m2e.android.test
mvn com.github.github:site-maven-plugin:site -P release
cd ..
Once this has completed you are ready to switch the trunk to the new SNAPSHOT version:
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=<new version>-SNAPSHOT`
Please note: sometimes the Tycho "set-version" Maven goal doesn't update all the versions in your source code so you you should search for occurrences of the old release version number and manually replace them.
Run a test build and push the updated code to the master repo:
mvn clean verify
git commit -am "Candidate <new version>-SNAPSHOT"`
git checkout master
git merge release-<version>
git push origin master
Lastly, you should update the iuVersion in the catalog.xml m2e Discovery Catalog descriptor in-line with the new release version. See instructions here for more details: