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.
