On Thursday, September 17, 2015 at 1:04:15 PM UTC+1, Daniel Beck wrote: > > > On 17.09.2015, at 13:02, Tom Fennelly <[email protected] <javascript:>> > wrote: > > > while other plugins are just "dependency" plugins … and are dependencies > … Jenkins core itself. > > These do not exist today.
Sure, I'm just suggesting that there should be some sort of distinction of different types of plugins. They all seem to be treated the same atm, which seems wrong to me. > If you need them for other changes, this will need to be considered > separately. Remember, every plugin, even the bundled ones, can be disabled, > which would in this case break Jenkins. Maybe the solution to that issue > even blocks finalizing this one? > Well I do think these things need to be considered at some stage, but not as blockers for this (imo). Jenkins has always been at varying degrees of mercy of people disabling plugins at a bad time, right? Sure, this would be more unmerciful though :) -- 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/9ba3271e-c01f-43b8-9019-54b0b7f4946c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
