On Thu, Sep 17, 2015 at 11:49 AM, Tom Fennelly <[email protected]> wrote: >> Jenkins core cannot depend on a plugin, this makes no sense. > > I still don't get why it's such a no-no.
Violates the very notion of what a “plugin” is. By definition, plugins depend on core, and core does not depend on any plugin. > if […] this restriction is imposed then we need > to rethink how we do the UI stuff in Jenkins core (wizard The plugin installation wizard is obviously a special case. Either it is itself a plugin which some bootstrap code installs (my preference), or it is written so as to avoid using any libraries not already in core. > config page changes Either JENKINS-26464 (my preference), or written so as to use no new dependencies, or figure out how to make `jenkins-module`s work for your purposes, or register an extension which swaps out a plain UI. -- 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/CANfRfr0jt88wfzbFecPnZyfWqDT5Ha7%2B_mnveQo37XE%2B79jYJQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
