Yeah, that sounds a bit fishy. In addition, even if the plugin archive didn't include the dependency and required the user to install it in their CLASSPATH some other way (which would be ugly), it seems like such a license would also infect derivative works (such as a plugin that uses the library). Without seeing the license in question that's only a guess, but it would not be surprising.
----- Original Message ----- From: [email protected] To: [email protected] At: Jan 30 2013 13:53:31 So, you can distribute it on the Jenkins update server inside your plugin archive, but you can't put it into a Maven repo? That doesn't seem to jive with me. On Wed, Jan 30, 2013 at 11:49 AM, Scott Cowan <[email protected]>wrote: > The terms of the third party library license doesn't allow for that. > > > On Wednesday, January 30, 2013 1:30:52 PM UTC-5, Jesse Glick wrote: >> >> On 01/30/2013 10:26 AM, Scott Cowan wrote: >> > 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. >> >> So deploy that dependency to the Jenkins repository, then you are all >> set. >> > -- > 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. > > > -- Website: http://earl-of-code.com -- 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.
