On Thursday, September 17, 2015 at 5:38:37 PM UTC+1, Jesse Glick wrote: > > On Thu, Sep 17, 2015 at 11:49 AM, Tom Fennelly <[email protected] > <javascript:>> 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. >
But is it not possible to redefine what it means to be a plugin? BTW, it is possible for us to do a totally self contained install wizard that has everything it needs bundled inside it. I just think it's a waste if we are going to be doing other things too in core. -- 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/609c84fc-1bf8-4bc1-8d82-5510b76de99e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
