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]
