It's no longer relevant whether a plugin is bundled for whether it can be uninstalled. However, when you (schedule to) uninstall a bundled plugin, it'll just get reinstalled on restart.
This check needs to be reinstated in addition to the dependencies check.
I've no problem with changing this to never allow bundled plugins to be uninstalled (it's easy), but I am curious to know exactly what problem it is causing? The only way you should be able to uninstall a plugin (bundled or otherwise) is if there's no other installed plugin depending on it.
Actually, I didn't think this would be possible. I thought I introduced the concept of a "core" dependency and that this was added to all bundled plugins. Anyway ... just a thought and something else to check when fixing this.
Tom FENNELLY The problem is that the behavior is unexpected. Rather than actually removing the plugin, you only effectively reset its version to the one that comes bundled. So changing back to not allowing this (while we still have bundled plugins) makes sense IMO.
I think this is still an issue. I am running 2.176.2 and I tried to uninstall the LDAP plugin. It lets me try, and I even tried actually deleting the files from /var/lib/jenkins/plugins, but after restarting, it comes back.
Most things about plugin management have changed in the almost three years this was filed. Please create a new issue, and describe what happened in detail there.
MostMany things about plugin management have changed in the almost three years this was filed. Please create a new issue, and describe what happened in detail there.