I just ran into the same issue.
surefire-providers [1] has variables in it's pom which i think are somehow
causing the behaviour you're seeing:
<dependencies>
<dependency>
<groupId>${project.groupId}</groupId>
<artifactId>surefire-api</artifactId>
<version>${project.version}</version>
</dependency>
</dependencies>
I uncommented the dependency section for that pom in my local repository and
all works fine then.
Regards
Jorg
[1]
http://mirrors.dotsrc.org/maven2/org/apache/maven/surefire/surefire-providers/2.0/surefire-providers-2.0.pom
On 5/15/06, Fisher, Michael (IT) <[EMAIL PROTECTED]> wrote:
We changed this to ${module_version} and it seems to work. What would
have
happened to break this?
Thanks,
Mike
-----Original Message-----
From: Fisher, Michael (IT)
Sent: Monday, May 15, 2006 11:59 AM
To: 'Maven Users List'
Subject: [M2] New surefire release breaks ${version}??
Hello,
It looks like the new surefire release (2.2) has broken the
externalization
of the pom.xml <version> element. Can anybody else confirm?
We are getting the following errors:
required artifacts missing:
org.apache.maven.surefire:surefire-api:jar:8.9.2
for the artifact:
dummy:dummy:jar:1.0
from the specified remote repositories:
[ our internal maven proxy repositories ]
Path to dependency:
1) dummy:dummy:jar:1.0
2) org.apache.maven.surefire:surefire-junit:jar:2.0
3) org.apache.maven.surefire:surefire-api:jar:8.9.2
Why is the surefire-api looking for the version I specified in my pom?
Running mavan as such: mvn test -Dversion=8.9.2
With a pom.xml as:
<version>${version}</version>
Thanks,
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
