What is needed is a way for plugins to identify that they are extensions for a specific plugin (as differentiated from direct depending on)
That way when you select the scm-api plugin you would also have a visual indicator that the git, subversion and mercurial plugins are designed to work with this API... Better yet is when you have plugin A and plugin B installed that it tells you that plugin C is designed to be a functionality connector between A & B... The issue is one of discovery. People use optional dependencies to put the connector stuff in say plugin B, so when you have A & B installed the connector functionality works. But better is to keep A & B with no knowledge of each other and then have C (with a hard dependency on both) provide the interconnect functionality... of course how do you know to install C in the first place? On 20 February 2014 15:35, Stephen Connolly <[email protected] > wrote: > They are certainly an issue when it comes to plugin upgrades and compat > testing > > > On 20 February 2014 14:44, Jesse Glick <[email protected]> wrote: > >> On Wed, Feb 19, 2014 at 8:07 PM, Patrick Higgins >> <[email protected]> wrote: >> > write a plugin that has >> > optional dependencies on several SCM plugins and provides the branch >> > information for a build based on the SCM plugins it finds at runtime. >> >> Rather write a plugin with no dependencies which defines this API and >> nothing more, and have various SCM plugins depend on it. >> >> (And @Daniel yes I consider optional dependencies to be problems.) >> >> -- >> 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. >> > > -- 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.
