have you tried wiping out $JENKINS_HOME/war as that may not be fully clean (it's where the .jar extracts all of the .war contents to?
On 25 October 2013 12:47, Federico Fissore <[email protected]>wrote: > > Il giorno giovedì 24 ottobre 2013 11:00:19 UTC+2, Vincent Latombe ha > scritto: > >> Probably a side-effect of the switch from winstone to jetty for the >> embedded container. Maybe there is something in your system that prevents >> jetty from initializing properly? >> >> > I thought that as well but I can't guess what. Also worth mentioning is > that starting clean (jenkins home freshly created) works fine, so it's > something in my config maybe? Or some plugin? Considering I cannot upload > it somewhere, what kind of info can I provide to spot the bug? > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
