On Mon, Nov 18, 2013 at 7:56 AM, Mads Mohr Christensen <[email protected]> wrote: > If I want to build the support into the promoted builds plugin, then I > run into a cyclic dependency problem. Parameterized trigger plugin is > depending on promoted builds plugin and I need to depend on the > parameterized trigger plugin.
Split the integration between these two plugins out into a third plugin. Then there will be no cyclic dependencies. (And you no longer need an optional dependency, which is always problematic.) The main problem then becomes mechanically notifying users of older versions of parameterized-trigger that when updating they should also install this new plugin, so that they do not lose functionality without being notified. https://issues.jenkins-ci.org/browse/JENKINS-19508 The only other alternative is to add the new functionality into parameterized-trigger, not promoted-builds. -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
