On Fri, Oct 9, 2015 at 4:19 AM, Victor Martinez <[email protected]> wrote: > In order to support the workflow plugin those dependent modules should be > part of every plugin?
Yes. The `workflow-step-api` plugin was expressly designed to be small and devoid of UI so that it would be an unobjectionable dependency. Optional dependencies cause lots of problems and should be avoided. > I like the idea of reducing the dependencies between plugins in order to use > the Configuration as Code paradigm without worrying about those dependent > plugins Why are you worrying about dependent plugins? When you include a plugin in your set, include its transitive dependency graph (as the Plugin Manager UI would). If the system you are using for enumerating plugins does not provide a trivial way to flag & correct missing transitive dependencies, fix that system. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0He8%2BWKXOUfSTMBE48YmMaoAoaK_zdiowveg01OA8Mvg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
