In a pom I agree, but from the CLI you can run checkstyle:check. -----Original Message----- From: Jason Dillon [mailto:[EMAIL PROTECTED] On Behalf Of Jason Dillon Sent: Monday, April 09, 2007 3:36 PM To: Maven Developers List Subject: Re: Checkstyle, maven-checkstyle-plugin and LGPL
On Apr 9, 2007, at 8:39 AM, Brian E. Fox wrote: >> 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> ? IMO is a bad idea to omit groupId anyways... I think that you should always fully qualify plugins with their groupId + artifactId (and version, or use pluginMangement for that). --jason --------------------------------------------------------------------- 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]
