Agreed, changing web.xml is not a blocker for backporting On Tuesday, March 27, 2018 at 4:54:17 PM UTC+2, Jesse Glick wrote: > > On Tue, Mar 27, 2018 at 10:41 AM, Oliver Gondža <[email protected] > <javascript:>> wrote: > > the possible breakage is limited to the people that > > are using custom [web.xml] > > Yes. (Is this even supported?) > > > and only when they use it to pass system properties > > I do not think so—if they use an old `web.xml` with the new > `jenkins-core.jar` then it will try to attach `SystemProperties` (the > outer class), which is no longer a `ServletListener` so I presume this > would fail startup. > > > the people with custom web.xml needs to change it every now and then so > the > > real question is if asking them to do so in one LTS line is such big > deal. > > Otherwise they would just need to change it on upgrade to (e.g.) > 2.119.1, so what is the difference? Just something we mention in the > upgrade guide. >
-- 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/28f467bc-6c63-4032-9beb-5262590134b1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
