On 08/21/2012 12:28 AM, Slide wrote:
all you need to do is make sure it has its own version and put that version in
your pom.xml for the plugin
Unfortunately it is a bit messy with the current Jenkins parent POM design. You
can either
1. Use the desired *-SNAPSHOT version of org.jenkins-ci.plugins:plugin in <parent>. But 'mvn install' on the Jenkins root POM does not install this because there is no
<module>plugin</module> (why??), so you need to also 'mvn -f plugin/pom.xml' install.
2. Override the versions of each dependency (jenkins-core, jenkins-test-harness, etc.) in your POM. Does not need org.jenkins-ci.plugins:plugin to be built but involves a
lot of redundancy.
There was a recent thread on this list suggesting that the plugin parent POM use a variable ${jenkins.version} to pick the versions of all Jenkins artifacts. We use a
parent POM like this for CloudBees plugins and it is much more convenient: you can simply say 'mvn -Pjenkins.version=1.480-SNAPSHOT clean hpi:run' without editing pom.xml
at all, or define profiles in ~/.m2/settings.xml for particular Jenkins versions like LTS, etc.
