Probably the same causes http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-675

Lester Ward wrote:
Ben Walding wrote
So... I'd take a look at your $REPO/commons-util/jars/commons-util-final.jar


Good call, Ben.

The issue was that my project was using an older version of commons-util. It
must be that Maven sets up the classpath to use the project dependencies
first, then the plugin dependencies. This seems backwards to me, because it
means that the project can override the plugin. There are arguments I can
see that this is desirable, but I think overriding the plugin classes is a
bad thing, because it means the plugin is not predictable and that any
problems like the one I had will be impossible to diagnose without access to
the project.

-- Norbert Pabiś



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to