Closed therewillbeblood closed 12 years ago
Hi Florent,
Frankly, I won't try to test my plugin against every weekly releases of jenkins (I however started the plugin compatibility tester (https://wiki.jenkins-ci.org/display/JENKINS/Plugin+Compatibility+Tester) for this purpose) : this would represent much of a burden !
Moreover, to help you a bit, I heard here and there that the jenkins version you're testing against is not the more stable the jenkins team has released (see https://twitter.com/#!/aheritier/status/200341196479016960) Could you try with 1.461 ? In all cases, I assume it works in latest LTS (1.447.1) : I'm using the plugin right now on this version :-)
Hi Frédéric,
i understand your POV, and the plugin compatibilty tester is a great idea.
I used 1.463 because there are some bug fixes in that release that i needed. FYI, the plugin won't build with 1.461 either (same error as 1.463), but you are right, 1.447 builds fine.
Thanks, Florent
Thanks for your feedback though.
I'll keep an eye on future releases (particularly 1.464 which would maybe fix the java 1.5 problems) in order to see if this is only a temporary glitch in jenkins core or if there is really an incompatibility starting from a given core version.
hi,
i checked out the lates commit d59c49ce1b66089c67b8d2b651f72184f032af6b on master. Building from scratch works well. However, changing jenkins plugin version in the pom.xml file from:
Cause the plugin not to build anymore:
is this aknown issue?
thanks