At the end of the link quoted below: > a bridging api (which can reside within the same project - so can be hosted at apache) >will be used to access these LGPL stuff to clearly show its optional behaviour
This is probably the simplest thing to do. Make a bridging API that sits at Mojo and the Apache plugin calls this bridging API. Moving the whole plugin will cause total havoc on existing builds. (As would purging old versions of it) -----Original Message----- From: Jerome Lacoste [mailto:[EMAIL PROTECTED] Sent: Monday, April 09, 2007 5:40 AM To: Maven Developers List Subject: Re: Checkstyle, maven-checkstyle-plugin and LGPL On 4/9/07, Jason Dillon <[EMAIL PROTECTED]> wrote: > Hey, I was just looking around at Checkstyle and noticed that it is > licensed as LGPL. Is this legit? I was under the impression that > Apache soft ware could not directly use any LGPL or GPL licenses > software... which the maven-checkstyle-plugin is clearly doing. [...] > I personally have no love for GPL/LGPL, why such hate ? :) > but I was a little surprised > when I noticed that Checkstyle is LGPL and that the maven-checkstyle- > plugin is importing classes from that package and referening them > directly... which I thought was a big no-no for ASF projects. > > Anyone know what's up? http://wiki.apache.org/jakarta/Using_LGPL'd_code So basically no. I doubt the checkstyle code will be relicensed. So the plugin should be rewritten or moved to another site (and the repositories cleaned up. That should make for a fun exercise). :( J --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
