In order for this to work, I think maven needs to support relocations of plugins. This currently doesn't work.
Does this mean ALL versions of checkstyle, including those already released must move? That's the part that will be most disruptive. -----Original Message----- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Monday, April 09, 2007 10:37 AM To: Maven Developers List Subject: Re: Checkstyle, maven-checkstyle-plugin and LGPL On 4/9/07, Brian E. Fox <[EMAIL PROTECTED]> wrote: > 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) It's the "optional" part that is important. Nothing from Apache should silently pull in LGPL dependencies. Moving the plugin to Codehaus is probably the best option. If it stays here, we'd have to make the Checkstyle dependency 'optional' and require the user to explicitly add it to his build. On a related topic, does Maven find plugins in org.codehaus.mojo without any extra configuration, or do you have to add the <groupId> ? -- Wendy --------------------------------------------------------------------- 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]
