ok, there is already a plugin that include the libdtkit https://github.com/jenkinsci/dtkit-plugin.
Maybe I could move xUnit dependencies from libdtkit to dtkit-plugin Il giorno mercoledì 2 maggio 2018 16:33:50 UTC+2, Jesse Glick ha scritto: > > On Wed, May 2, 2018 at 9:29 AM, 'Nikolas Falco' via Jenkins Developers > <[email protected] <javascript:>> wrote: > > So you suggest to move code from DTKit into xUnit plugin > > IIUC the recommendation was simply to take the existing library and > repackage it as a plugin (with no user-facing features). That allows > it to be independently updated. `jar`-packaging means that every > plugin depending on bundles its own copy of the library, and > library-defined types cannot be shared. Switching to an API plugin > also avoids the need for special tricks to accommodate JEP-200 in > Jenkins 2.102+. > > > https://jenkins.io/doc/developer/plugin-development/dependencies-and-class-loading/ > > -- 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/feb3abc7-aebd-4dc2-bdd4-1a3fa9d35dd7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
