On Fri, Jan 22, 2016 at 4:28 AM, Stephen Connolly
<[email protected]> wrote:
> Well we started our internal parent pom at 1.400 so as long as *you* consult
> the older versions of that you should be able to infer the correct versions
> of hpi plugin and stapler plugin to build against such a really old core...
FWIW I have in my `~/.m2/settings.xml` profiles such as
<profile>
<id>jenkins-565</id>
<properties>
<jenkins.version>1.565.3</jenkins.version>
<hpi-plugin.version>1.106</hpi-plugin.version>
<java.level>6</java.level>
</properties>
</profile>
It might be worth writing and testing a series of such profiles for
all reasonably recent LTS lines and adding them to `plugin-pom` for
everyone to benefit from. Then without any work, you could check your
plugin’s behavior against a different line very easily:
mvn -Pjenkins-642 clean verify
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr025xip7k507HHZpYrAzLYbTcJtv9xgnymHNB6NepaJMw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
