On Tue, Aug 5, 2014 at 1:30 AM, Michael Nothhard <[email protected]> wrote: > The dependencies are listed in the POM but the jar's aren't available in a > public maven repo
If the JARs are freely redistributable, then the preferred approach is to get them into Central. If they cannot go into Central, they could be deployed into the Jenkins repository. Assuming they are not redistributable, then the plugin should not declare static dependencies on them. Instead it should create a URLClassLoader which loads the JARs from a location specified in plugin global configuration. Then you can access classes and methods in the JARs using reflection. Alternately, write the integration code in Groovy (hoping that statically unknown types will be tolerated by the Groovy compiler, or using dynamic typing), and load those Groovy classes from the same URLClassLoader. -- 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/d/optout.
