Elexis 3 Base Repository
Created the pom.xml like this
mvn org.eclipse.tycho:tycho-pomgenerator-plugin:generate-poms -DgroupId=ch.elexis.base -Dversion=3.0.0-SNAPSHOT
Then I manually adjusted the pom.xml’x in the base folder and in the ch.elexis.base.ch.p2site
- There is handy tool to see InstallableUnit in P2-Repositories. See p2-browser.
It can be easily launched on the console using javaws http://ifedorenko.github.com/p2-browser/javaws/com.ifedorenko.p2browser.jnlp
- The p2 site contains only the artifacts built inside this repository.
- No Eclipse RCP product is built, as we assume that the core product is distributed using the Elexis 3 core.
- Decide how the release naming will work
mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=3.0.1-SNAPSHOT
gives me a NPE.
Here some pointers.
- http://code.google.com/a/eclipselabs.org/p/spray/wiki/DevGuide_Release
- https://docs.sonatype.org/display/M2ECLIPSE/Staging+and+releasing+new+M2Eclipse+release
- https://openflow.stanford.edu/display/Beacon/Releasing
- http://maven.apache.org/maven-release/maven-release-plugin/examples/update-versions.html
- https://community.jboss.org/en/tools/blog/2011/09/17/coping-with-versions-in-large-multi-module-osgi-projects