On Thu, Jul 11, 2019 at 6:14 AM Tony Noble <[email protected]> wrote: > how to create plugins that are essentially subclasses of other plugins (which > is what would need to happen if xtrigger was migrated to be a plugin)
Completely routine; you just declare a Maven dependency and you are done. Certainly less exotic and trouble-prone than the current design. https://jenkins.io/doc/developer/plugin-development/dependencies-and-class-loading/ > if it's even possible to do all this without breaking existing user > configuration. Assuming Java package names are left untouched, there should be no effect on user settings. At any rate, > I'm not sure how the process would work for a lib rather than a plugin. The release process for the library is identical to that for a plugin: mvn release:{prepare,perform} The additional step in the current design is that you then need to go to all the plugins using the library, update their dependency, and release them too. If we switched the library to a plugin, it would suffice to just release it—anyone accepting that update would get the new behavior for all the feature plugins, since these would no longer be physically bundling the library. -- 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/CANfRfr3kSjVPmxE%3DY42Mvari_pNtMHOCR3hKDDLGAoqnm8R8BQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
