I have seen this occur as well. First project to use a plugin picks the
version for everyone else in the reactor.
-Original Message-
From: Brad O'Hearne [mailto:[EMAIL PROTECTED]
Sent: Saturday, June 30, 2007 2:14 PM
To: Maven Users List
Subject: Re: repeated problems with
Thanks to a friend, who hopefully will post a description of the problem
later this weekend to the list, the problem was identified and a
workaround found. The problem is maven, and lack of class-loading
isolation for plugins in child modules of a parent project. In a
nutshell, the first versio
You should specify a version for the plugin in your pom. That is the
only way to know for sure which version will be used.
Brad O'Hearne wrote:
It isn't the proxy. I've removed the proxy completely from the picture
and it hasn't helped. In fact, I've completely deleted the
org/apache/maven/plu
It isn't the proxy. I've removed the proxy completely from the picture
and it hasn't helped. In fact, I've completely deleted the
org/apache/maven/plugins from my local repo, and for some reason it is
trying to pull the 2.0-alpha-1 version of the maven-dependency-plugin.
Additionally, this pro
The configuration seems right and since it sporadically succeeds, seems
to imply it's correct. I'm guessing this could be a problem with your
proxy. Are you able to try it somewhere you don't need a proxy?
-Original Message-
From: Brad O'Hearne [mailto:[EMAIL PROTECTED]
Sent: Friday, June
