On Fri, May 30, 2025 at 4:15 PM Basil Crow <[email protected]> wrote:
> Even if […] someone were to extract Guice from core into a Jenkins library > plugin […] I think we would still be unable to upgrade the Guice library plugin from 6 > to 7 unless we were to > > > fix MNG-8027, officially drop support for the Jenkins Maven plugin > (which is still being used by some people), or find some other solution to > keep the Jenkins Maven plugin working with Guice 7. My expectation in that scenario is that we would have a Guice 6 library wrapper plugin plus a Guice 7 plugin, and consumers would pick which one they wanted to depend on, with `maven-plugin` staying on 6 for now. Part of removing it from core would mean avoiding any case where Guice types are exposed from Jenkins APIs and thus need to be shared amongst plugins, so it would be safe to have both versions loaded at once (unless Guice does bad things with `Thread.contextClassLoader`). Note https://lists.apache.org/[email protected] (I would like to remove both jclouds and Guice from `artifact-manager-s3` anyway). -- 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 visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3bAZ1meaq%2ByZp9_qF-V14Bsq6-GG5L-CNC30hM-G0nVg%40mail.gmail.com.
