Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.3
-
Component/s: None
-
Labels:None
Description
This pom contains :
<dependency>
<groupId>${project.groupId}</groupId>
<artifactId>surefire-api</artifactId>
<version>${project.version}</version>
</dependency>
This generate strange error in certain case.
I have replaced with :
<dependency>
<groupId>org.apache.maven.surefire</groupId>
<artifactId>surefire-api</artifactId>
<version>2.0</version>
</dependency
And works fine.
The stack trace says
WARNING] Unable to get resource from repository central (http://repo1.maven.org/maven2)
[DEBUG] Unable to download the artifact from any repository
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.maven.surefire -DartifactId=surefire-api \
-Dversion=2.4.1 -Dpackaging=jar -Dfile=/path/to/file
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:2.4.1
org.apache.maven.surefire:surefire-api:jar:2.4.1
from the specified remote repositories:
rec-ap2 (http://57.200.214.247/maven2),
central (http://repo1.maven.org/maven2),
continuum-repo-snapshots (http://57.200.214.247/continuum-repo/),
apache.snapshots (http://svn.apache.org/maven-snapshot-repository),
rec-ap2-snapshots (http://57.200.214.247/snapshots)
Issue Links
- is duplicated by
-
SUREFIRE-218
Unable to use 2.3-SNAPSHOT
-
- relates to
-
MNG-2339
${project.*} are interpreted in the wrong place
-
Activity
Hi,
Arghhh this kind of error always appends to me 
IMHO, it's more a MNG issue than a surefire one.
Note, I have already seen this properties resolution trouble with transitive dependencies in some internal projects.
I don't remember the case as I believe it was something like :
pom.xml (foo:parent:1.0-SNAPSHOT)
api/pom.xml (foo:api:${project.parent.version})
impl1/pom.xml (foo:impl:${project.parent.version})
In the root pom, I defined a dependency in dependencyManagement
with foo:api:${project.version}
version in api/pom.xml and impl1/pom.xml defined with ${project.parent.version}.
a dependency in impl1/pom.xml to foo:api.
This configuration generated same trouble when using foo:impl:${version.number} in a other project.
I will try to provide a test (if enough time).
–
Olivier
Thanks for investigation my workaround is to set surefire version to 2.1.3 in the module called dotw-webapp.
IMHO, it's more a MNG issue than a surefire one.
Note, I have already seen this properties resolution trouble with transitive dependencies in some internal projects.
I don't remember the case as I believe it was something like :
pom.xml (foo:parent:1.0-SNAPSHOT)
api/pom.xml (foo:api:${project.parent.version})
impl1/pom.xml (foo:impl:${project.parent.version})
In the root pom, I defined a dependency in dependencyManagement
with foo:api:${project.version}
version in api/pom.xml and impl1/pom.xml defined with ${project.parent.version}.
a dependency in impl1/pom.xml to foo:api.
This configuration generated same trouble when using foo:impl:${version.number} in a other project.
I will try to provide a test (if enough time).
–
Olivier
Thanks for investigation my workaround is to set surefire version to 2.1.3 in the module called dotw-webapp.
Attached the full stack trace.
This happend in the situation
pom.xml
module / pom.xml
Building mvn clean install from root works.
Just checkout the the module running mvn clean install then the stack trace appends.
Thanks to check and/or fix
–
Olivier