On Thursday, September 17, 2015 at 3:59:46 PM UTC+1, Jesse Glick wrote: > > So my running proposal > ยท nothing, nada, in `WEB-INF/plugins/` > > > dependencies of "feature" plugins OR Jenkins core itself > > Jenkins core cannot depend on a plugin, this makes no sense.
(There > are `jenkins-module`s shared among core and plugins, but the user has > no control over their installation, they are just in `WEB-INF/lib/`.) > I think maybe KK needs to chip in here. I thought I outlined a scenario where I thought it does make sense from the pov of how we plan to do some UI enhancements going forward (and KK seemed to think so too). I still don't get why it's such a no-no. Well, I do get the issues re it being possible for someone to disable them, but that to me is a different issue and goes back to my point about the lack of distinction between different kinds of plugins and what people are allowed to do to them, how the appear in the PM etc. Anyway, if this is the approach and this restriction is imposed then we need to rethink how we do the UI stuff in Jenkins core (wizard, config page changes etc). That's another discussion I guess, but does seem to indicate to me that there's a hole (in this logic, or my understanding :) ) that needs filling. jenkins-modules are available but don't seem to meet the requirements (easy exposing of web resource without Java hackery) and can't be updated (require a new Jenkins). -- 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/bc405bf1-a1f4-48a3-8ff9-83032232a9c4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
