I'd like to make the debian package that's built by jenkins have a unique
version number that reflects the jenkins build number or some other meaningful
version string.
Currently it's stuck at "8-SNAPSHOT" because this started off being tied to the
launchpad build. It's not even related to launchpad any more, so I'd like to
fix this versioning issue now.
( Side note question, should it be moved out from under
contrib/launchpad/debian to contrib/debian as it's not related to launchpad
anymore? )
What is the current mechanism used by the jenkins build to inject version
numbers into pom files to obtain meaningful versions for the output artifacts?
I've always mvn -DBUILD_NUMBER=${BUILD_NUMBER} clean versions:set to set
newVersion in the pom, but I don't see this used anywhere in the sling source
tree.
Lastly, once the .deb package is built with an appropriate version number,
would it be possible to get this pushed to nexus as part of a release so that
it's available as a downloadable artifact?
Nexus does support exposing debian packages as artifacts via the deb plugin, so
my question is, could this be done, rather than "is it possible".
thanks
-Bruce
