> On 03.05.2016, at 03:08, Jay Howard <jay.patrick.how...@gmail.com> wrote: > > For instance, I'd like to remove the Subversion plugin but I'm blocked > because the Parameterized Trigger plugin has an "optional" dependency on it.
A known limitation of the current UI. > Also, a surprisingly large number of plugins seem to depend on on the > "Windows Slaves" plugin that have nothing to do with Windows. Windows Slaves used to be part of core, then its functionality was moved to a plugin in 1.547. The problem is, we don't know whether a plugin built against 1.546 or earlier uses its features, so Jenkins treats those as having a dependency on the 'detached' plugin. Not doing this may break plugins with cryptic error messages. There is currently no way to work around this other than change all plugins built against an older Jenkins release to build against 1.547+ so they need to declare an explicit dependency if they use the plugin's features. Note that you may decide to be clever and just delete the Windows Slaves plugin from disk. Don't do that. If it doesn't already cause breakage today, there's a change coming soon that would definitely make all plugins with dependencies fail to load on startup. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/5A151AFA-54E0-48FA-BD95-F8D39DB9AF90%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
