On Fri, May 30, 2025 at 11:27 AM 'Jesse Glick' via Jenkins Developers <[email protected]> wrote: > Better still (IMHO) would be to remove the Guice dep from core
This problem is orthogonal to the one being discussed in this thread, I think. Even if, by some great effort, someone were to extract Guice from core into a Jenkins library plugin—with Maven, Artifact Manager on S3, JClouds, and the like consuming it via plugin-to-plugin dependency—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. The fundamental problem is that Guice 7 removes an old capability (javax package support), necessitating all consumers to have migrated from the old capability to the new—while Maven has not migrated, and has no plans to in the near future. Guice 6 supports both the old and new capabilities. -- 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/CAFwNDjo6Me0jgjMrwxoY28iPzRAQiE-H2fQ8mcrwcyaTh%3DROUw%40mail.gmail.com.
