On 09.10.2015, at 10:19, Victor Martinez <[email protected]> wrote:
> In order to support the workflow plugin those dependent modules should be > part of every plugin? If that's the case, is there any planning to add those > features as part of the jenkins core? 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 Adding to what Jesse wrote: It should be fairly trivial to read the plugin dependencies from the HPI files and recursively (transitive dependencies) add them to your installation. I think I even did that as a bash script once. -- 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/650B7BCA-903F-40D3-9235-3E2D4E6E54E3%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
