Thanks for the info, Jesse and Scott. We will proceed with getting our plugin into shape to be contributed. We'll likely end up using stubs, as Jesse suggested, so that the plugin can be compiled separately from RTC, and functional tested wrt Jenkins (but not RTC) at package time.
When it comes to contributing the source, is it better for us to put it up in a separate github project and pull from there, or open one directly under jenkins-ci to start off? Thanks, Nick On Wednesday, January 30, 2013 10:26:45 AM UTC-5, Scott Cowan wrote: > > Hi, > > I'm working on a new plugin that has a build dependency on a third party > library that isn't available in any public maven repository. I'd like to > host it at jenkins-ci.org but wondering if I can build it myself and > "release" the .hpi file so it is available by default in a Jenkins > install. Is this possible, and how does it work? > > Thanks in advance, > Scott > -- 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.
