2013/1/31 Scott Cowan <[email protected]> > Jesse, slide & Kevin, > > Thank you all for your input. My understanding is that the terms of use > in the license for Rational Team Concert does not allow for > redistribution. I am getting clarification on that, and whether or not > deploying it to the Jenkins repository constitutes redistribution. There's > a link to the license from this link, but you have to have a jazz.netaccount. > Feel free to check it out if you're curious, but be forewarned it > is thorough. ;-) > > > https://jazz.net/downloads/rational-team-concert/releases/4.0.1/RTC-BuildSystem-Toolkit-Win-4.0.1.zip > > We really want to integrate our build support with that of Jenkins. The > two tools complement each other nicely. IBM and Rational really do promote > open source software and integrations with our products. And if jazz.netcan > host a public maven repository, we will probably go that route. In the > short term we're just wondering of we can work around the problem by > building it ourselves and releasing it periodically. > > We're thinking we won't distribute our libraries inside our plugin > archive, but rather have a global configuration property that will point to > our build toolkit install directory. Kind of like other source control > systems require pointing to the command line executable. The difference is > we want to create a tighter integration than just with source control. We > want to also integrate with our own build results and work items, and none > of this integration is currently available in our command line tool. >
Would then be even better to provide an auto-installer for this runtime > > Does this make sense? Am I the first person to request this? Again, > thanks for any input/advice you can provide, > Scott > > > > On Wednesday, January 30, 2013 2:43:50 PM UTC-5, Jesse Glick wrote: >> >> On 01/30/2013 02:24 PM, KEVIN FLEMING (BLOOMBERG/ 731 LEXIN) wrote: >> > even if the plugin archive didn't include the dependency and required >> the user to install it in their CLASSPATH some other way >> >> …in which case the Maven build probably does not need it, either. >> > -- > 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.
