-
Bug
-
Resolution: Fixed
-
Major
-
2.0-beta-1
-
-
2.181
The plugin manager UI does not allow disabling or removing optional dependencies, i.e. dependencies that are declared by plugins to be not strictly necessary for their use.
This should be possible, maybe with a warning that not all features of the depending plugin will be available afterwards.
- is duplicated by
-
JENKINS-44013 Unable to uninstall plugin that is an optional dependency
-
- Resolved
-
-
JENKINS-45906 Optional dependency blocks plugin removal
-
- Closed
-
-
JENKINS-46930 Update Center prints warnings about plugins with optional deps when deleting plugins
-
- Resolved
-
- relates to
-
JENKINS-27177 There should be a command line mechanism to disable plugins
-
- Closed
-
-
JENKINS-50885 BlueOcean should have an optional dependency on JIRA plugin
-
- Resolved
-
-
JENKINS-39598 MultiSCM/config.jelly passes descriptors=null
-
- Closed
-
- links to
[JENKINS-33843] It's not possible to disable/uninstall optional dependencies
Workflow | Original: JNJira [ 169838 ] | New: JNJira + In-Review [ 183659 ] |
Labels | Original: 2.0 2.0-beta | New: 2.0 2.0-beta newbie-friendly |
Link |
New:
This issue is duplicated by |
Summary | Original: It's not possible to disable optional dependencies | New: It's not possible to disable/uninstall optional dependencies |
Description |
Original:
The plugin manager UI does not allow disabling optional dependencies, i.e. dependencies that are declared by plugins to be not strictly necessary for their use. This should be possible, maybe with a warning that not all features of the depending plugin will be available afterwards. |
New:
The plugin manager UI does not allow disabling or removing optional dependencies, i.e. dependencies that are declared by plugins to be not strictly necessary for their use. This should be possible, maybe with a warning that not all features of the depending plugin will be available afterwards. |
Link |
New:
This issue relates to |
Link |
New:
This issue is duplicated by |
Link |
New:
This issue is duplicated by |
Workaround (untested): touch $JENKINS_HOME/plugins/unwanted.jpi.disabled