FYI The reason why the maven-bundle-plugin does not give advice on bumping the Bundle version is that it has not been implemented (refer AbstractBaselinePlugin) hence only public API changes are reported.
Has anyone managed implement a maven based release process in a CI environment with automagic version setting following the semantic versioning rules? The best I could see was to follow the Aries release process http://aries.apache.org/development/versionpolicy.html along with some modifications to the maven-bundle-plugin to recommend the bundle version bump. The bundle version bump recommendation could then be used to manually set the bundle version and it's corresponding module dependencies in dependent bundles thus the developer/release manager wouldn't have to try and determine what bundle and dependency versions were required by having to look through the package infos. I realise that this has been done in a non maven build environment www.planetmarrs.net/semantic-versioning-and-continuous-integration/ and http://www.liferay.com/web/raymond.auge/blog/-/blogs/semantic-version-reporting-tool-in-liferay-s-build. -- View this message in context: http://apache-felix.18485.x6.nabble.com/maven-bundle-plugin-and-baselining-tp5010417p5010586.html Sent from the Apache Felix - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@felix.apache.org For additional commands, e-mail: users-h...@felix.apache.org
