Maven 2 & 3

reporting plugin poms are retrieved from the wrong repository

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Duplicate
  • Affects Version/s: 2.0.8
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    1

Description

Pull the staged 2.4 into your local repo, and run surefire-report:report-only on a POM configured to use 2.4. The build will fail. Try again, this time running "mvn org.apache.maven.plugins:maven-surefire-report-plugin:2.4:report-only"

-----------------------------------------------------
this realm = app0.child-container[org.apache.maven.plugins:maven-surefire-report-plugin]
urls[0] = file:/c:/weirdlocalrepo/org/apache/maven/plugins/maven-surefire-report-plugin/2.4/maven-surefire-report-plugin-2.4.jar
urls[1] = file:/c:/weirdlocalrepo/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
Number of imports: 4
import: org.codehaus.classworlds.Entry@4891bb28
import: org.codehaus.classworlds.Entry@f8e44ca4
import: org.codehaus.classworlds.Entry@c51bc9e7
import: org.codehaus.classworlds.Entry@bece5185

this realm = plexus.core
urls[0] = file:/C:/devtools/maven-2.0.7/lib/maven-core-2.0.7-uber.jar
Number of imports: 4
import: org.codehaus.classworlds.Entry@4891bb28
import: org.codehaus.classworlds.Entry@f8e44ca4
import: org.codehaus.classworlds.Entry@c51bc9e7
import: org.codehaus.classworlds.Entry@bece5185
-----------------------------------------------------
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-surefire-report-plugin:2.4:report-only': Unable to find the mojo 'org.apache.maven.plugins:maven-surefire-report-plugin:2.4:report-only' in the p
lugin 'org.apache.maven.plugins:maven-surefire-report-plugin'
org/apache/maven/reporting/AbstractMavenReport

Issue Links

duplicates

Bug - A problem which impairs or prevents the functions of the product. MNG-3560 unable to use plugins that exist in multiple repositories

  • Major - Major loss of function.
  • 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-3383 Downloaded plugin dependencies influence project dependencies

  • Major - Major loss of function.
  • 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
Brett Porter added a comment -

when using a plugin repository that is not central (for example, to test a staged release), the POM is still searched for on central, rather than <pluginRepositories>. This is not found and causes the build to break.

Show
Brett Porter added a comment - when using a plugin repository that is not central (for example, to test a staged release), the POM is still searched for on central, rather than <pluginRepositories>. This is not found and causes the build to break.
Hide
Permalink
Brian Fox added a comment -

Dan, got a test case for this?

Show
Brian Fox added a comment - Dan, got a test case for this?
Hide
Permalink
John Casey added a comment -

This is the test scenario I built based on Dan's and Brett's descriptions. I have not been able to reproduce this problem using the attachment.

Show
John Casey added a comment - This is the test scenario I built based on Dan's and Brett's descriptions. I have not been able to reproduce this problem using the attachment.
Hide
Permalink
John Casey added a comment -

I'm unable to reproduce the problem at this time, using the attached report plugin. My configuration and usage of the plugin is in the report-usage project subdirectory, where I've also included the build output in debug mode from running the report via direct invocation using both prefix:mojo and fully-qualified notations. I also ran `mvn site` with this report included, and everything succeeded. I've even tried leaving out the reporting section of the usage POM, with no success in reproducing the problem.

If someone can shed some more light on the issue here, please attach a test case and reopen. I'm marking this fixed because Brett's comments seem to indicate that at one point he was able to reproduce the problem.

Show
John Casey added a comment - I'm unable to reproduce the problem at this time, using the attached report plugin. My configuration and usage of the plugin is in the report-usage project subdirectory, where I've also included the build output in debug mode from running the report via direct invocation using both prefix:mojo and fully-qualified notations. I also ran `mvn site` with this report included, and everything succeeded. I've even tried leaving out the reporting section of the usage POM, with no success in reproducing the problem. If someone can shed some more light on the issue here, please attach a test case and reopen. I'm marking this fixed because Brett's comments seem to indicate that at one point he was able to reproduce the problem.
Hide
Permalink
Paul Benedict added a comment -

John, can I recommend you keep this open and bump to 2.0.10? It will keep it on the radar for verification. If it truly can't be produced, then it should get a Cannot Reproduce state.

Show
Paul Benedict added a comment - John, can I recommend you keep this open and bump to 2.0.10? It will keep it on the radar for verification. If it truly can't be produced, then it should get a Cannot Reproduce state.
Hide
Permalink
John Casey added a comment -

I'm easy...

Show
John Casey added a comment - I'm easy...
Hide
Permalink
John Casey added a comment -

If we're going to take a real shot at fixing this, we need a test case that displays the problem. There is nowhere near enough information to reconstruct the issue from the comments and description above.

Show
John Casey added a comment - If we're going to take a real shot at fixing this, we need a test case that displays the problem. There is nowhere near enough information to reconstruct the issue from the comments and description above.
Hide
Permalink
John Casey added a comment -

Pushing to 2.0.11 so we can have a smaller set of high-value issues to target for the next release (2.0.10).

Show
John Casey added a comment - Pushing to 2.0.11 so we can have a smaller set of high-value issues to target for the next release (2.0.10).

People

  • Assignee:
    Brett Porter
    Reporter:
    Dan Fabulich
Vote (0)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: