On Mon, Sep 28, 2015 at 2:01 PM, Stephen Connolly <stephen.alan.conno...@gmail.com> wrote: > perhaps we could treat the older core plugins as being like the other > de-bundled functionality
Yes, this was my thought. Just as a plugin declaring a dependency on an older core gets an implicit dependency on any plugins subsequently split out, so too would it get an implicit dependency on any libraries subsequently made into plugins. Indeed there is little difference from the perspective of the plugin with the (possible) dependency whether that dependency happened to be defined in `org.jenkins-ci.main:jenkins-core`, some `jenkins-module`, or some random `WEB-INF/lib/*.jar`. -- 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/CANfRfr0g%3D%2Bq4cu4h9TOyqX0YCApgOPjJxT8SojcppJZPbm%2BfTQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
