Here is a convo I had with someone at Clover headquarters about licensing. He mentioned Maven integration before I did, so maybe he is on this list ;-):
-------8<---------- Hi Peter, > Sorry, but I am missing something. What about if a commercial > company wants to just 'use', not develop the open source > project which has freely licensed Clover? > The open source project by it's license requires no payment > in this case. Will the commercial company need a seperate > clover license costing $125.00 in this case? > My apologies - we haven't explained ourselves very well. As an example, consider the Maven open source project. Maven could obtain a $0 Clover license. This would allow the Clover binary to be distributed with the source distribution of Maven, for the sole purpose of contributing to the open source development of Maven. If a commercial company downloads Maven, and uses it to manage the build of their own project, they would not be licensed to use Clover for their project. They would indeed need a separate Clover license. Licensing for Clover is yet to be finalised. Our goal is to make Clover freely available for open source projects to use, while still providing us with some income from commercial users to support ongoing development of Clover. We welcome all feedback on how we can better achieve this balance. Regards, -Brendan ---- Brendan Humphreys Senior Software Engineer Cortex eBusiness http://www.cortexebusiness.com.au ----------8<---------------- -Peter ----- Original Message ----- From: "bob mcwhirter" <[EMAIL PROTECTED]> To: "Turbine Maven Developers List" <[EMAIL PROTECTED]> Sent: Saturday, June 15, 2002 12:09 PM Subject: Re: New Clover plugin > > > I'm eager to commit but I wanted to check with you first ... :-) > > > > Note: The only "issue" that I can see is that clover is free for all > > non-commercial projects only (however, Cortex, the company creating > > Clover seem ok for us to redistribute the clover jar). > > +1 if we can get definite clue as to license issues. > > Do we have lawyers to look at this kind of thing? > > > It is a plugin I'd like to see integrated in Maven as it is the best > > test coverage tool that I have seen and by far. The problem is that I > > don't know how I could write such a plugin with no impact on existing > > ones (core, test, doc). The same issue will happen with > > Jalopy/JRefactory (but it is easier for them as they don't need to > > modify the compile target, etc). > > Hopefully maven-ng will make plugins such as this > easier to do. > > -bob > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
