Le 17 sept. 2013 09:32, "mohan kumar Muddana" <mohanj...@gmail.com> a écrit : > > I assume the following commands will try to resolve, but not quite confident. > > mvn clean compile
Useless. Next command you give already includes the compilation phase. > mvn clean -DskipTests=true package Again, why would you skip the tests of your plugin? > > Also a failed/older plugin installation leaves the .jpi file as well exploded folder as it is. > So, deleting these older ones might also help it seems. > > What do you say? > > Thanks > Mohan > > On Tuesday, September 17, 2013 3:50:12 AM UTC+5:30, Jesse Glick wrote: >> >> On Mon, Sep 16, 2013 at 5:20 PM, evernat <eve...@free.fr> wrote: >> > It's WEB-INF/lib/classes.jar and they are now created in Jenkins for each >> > plugin, to be remoting friendly. >> >> So that is a possible explanation for the bug: the repacking might >> produce different content somehow. > -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
