Status: Open (View Workflow)
From a discussion with jglick in
When this mode is opted into, signal an error if any transitive dependency is not explicitly listed. Textually differentiate “feature” plugins that the user specifically wants, vs. plugins in that list that are only there as dependencies, and signal an error if there is a dependency entry which is not in the transitive dependency closure of any feature entry. (See discussion in
The referenced discussion in
I think my suggestion at the time was to require essentials.yaml to declare all plugins explicitly, but add a boolean transitive flag to each plugin entry and then fail the build if there are any plugins marked as transitive which do not have a hard (~ not optional) dependency chain from at least one nontransitive plugin in the list. Thus you can see at a glance which plugins are there because they offer some important feature, vs. being just along for the ride, and if you accidentally “orphan” some transitive dependency (for example because some routine plugin update finally picks up the holy grail of dropping the last hard dep on maven-plugin) then you will be alerted to the situation immediately and can delete the now-obsolete plugin (or decide you really wanted to keep it after all, and mark it nontransitive).
JENKINS-59148 was resolved as "Fixed", this gap still remains. In my opinion it would be desirable to implement this suggestion to improve transitive dependency management in Plugin Installation Manager Tool.
- relates to
JENKINS-59148 Add Functionality for Getting Latest Plugin Dependencies