Thanks Jesse & boa...@! I get it now. Does it make sense to get plugins to stop using libraries already in jenkins-core's dependency tree? i.e. are those libraries part of the contract?
If they can be considered guaranteed by jenkins-core, we can just remove the dependencies. If they can't, then we can create api-plugins for each of the popular ones, and get the plugins to depend on them. - Rahul On Monday, December 13, 2021 at 2:31:31 PM UTC-8 jgl...@cloudbees.com wrote: > On Mon, Dec 13, 2021 at 1:35 PM 'rsomas...@netflix.com' via Jenkins > Developers <jenkin...@googlegroups.com> wrote: > >> That suggests that Jenkins Core would prefer plugins to use slf4j-api. If >> that's the case, all plugins that depend on jenkins-core should use >> slf4j-api >> > > No, Jenkins core uses java.util.logging, and the great majority of plugins > do the same. slf4j-api is just there for a handful of third-party > components that require it. > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/0ce5a805-5abe-4c6b-a5b8-6cbc4604cdebn%40googlegroups.com.
