I recently updated to Jenkins 2.1 and removed a few of the "built-in" 
plugins we never use that were impossible to remove in earlier versions of 
Jenkins.  However, I'm finding myself unable to certain others because 
they're listed as "optional" dependencies of other plugins.

Am I wrong to assume that if plugin A has an "optional" dependency on 
plugin "B" that "A" being installed shouldn't block the removal of "B"?

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.

Also, a surprisingly large number of plugins seem to depend on on the 
"Windows Slaves" plugin that have nothing to do with Windows.

What am I missing?

-- 
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/74db24ab-2a5a-4552-9986-eaf72527c300%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to