Maven Surefire

surefire-providers-2.0.pom contains strange dependencies which generate error

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 2.3
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    2

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

Bug - A problem which impairs or prevents the functions of the product. SUREFIRE-218 Unable to use 2.3-SNAPSHOT

  • Blocker - Blocks development and/or testing work, production could not run
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
relates to

Bug - A problem which impairs or prevents the functions of the product. MNG-2339 ${project.*} are interpreted in the wrong place

  • Critical - Crashes, loss of data, severe memory leak.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Olivier Lamy added a comment -

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

Show
Olivier Lamy added a comment - 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
Hide
Permalink
Carlos Sanchez added a comment -

Can you attach the poms?

Show
Carlos Sanchez added a comment - Can you attach the poms?
Hide
Permalink
Olivier Lamy added a comment -

You want my poms ? or the surefire's in my repo ?

Show
Olivier Lamy added a comment - You want my poms ? or the surefire's in my repo ?
Hide
Permalink
Carlos Sanchez added a comment -

show me your poms

Show
Carlos Sanchez added a comment - show me your poms
Hide
Permalink
Olivier Lamy added a comment -

here my poms.

Show
Olivier Lamy added a comment - here my poms.
Hide
Permalink
Olivier Lamy added a comment -

The case happens when just checkout dotw-webapp module.
Not with all modules build.

Show
Olivier Lamy added a comment - The case happens when just checkout dotw-webapp module. Not with all modules build.
Hide
Permalink
Brett Porter added a comment -

the pom is valid. Maybe there is an issue in surefire's resolution - it'll need to be investigated. I've never seen this myself.

Show
Brett Porter added a comment - the pom is valid. Maybe there is an issue in surefire's resolution - it'll need to be investigated. I've never seen this myself.
Hide
Permalink
Olivier Lamy added a comment -

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.

Show
Olivier Lamy added a comment - 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.
Hide
Permalink
Olivier Lamy added a comment -

I don't know if related but look at http://jira.codehaus.org/browse/MNGECLIPSE-20
I see the same magic number 2.4.1 ?
–
Olivier

Show
Olivier Lamy added a comment - I don't know if related but look at http://jira.codehaus.org/browse/MNGECLIPSE-20 I see the same magic number 2.4.1 ? – Olivier
Hide
Permalink
Olivier Lamy added a comment -

IMO this is probably related too http://jira.codehaus.org/browse/MNG-2339.
–
Olivier

Show
Olivier Lamy added a comment - IMO this is probably related too http://jira.codehaus.org/browse/MNG-2339 . – Olivier
Hide
Permalink
Brett Porter added a comment -

this needs to be fixed in Maven itself.

We've already changed the POM to avoid the problem

Show
Brett Porter added a comment - this needs to be fixed in Maven itself. We've already changed the POM to avoid the problem

People

  • Assignee:
    Brett Porter
    Reporter:
    Olivier Lamy
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: