[
http://jira.codehaus.org/browse/MNG-3713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=145064#action_145064
]
Nathan Beyer (Cerner) commented on MNG-3713:
--------------------------------------------
A temporary work around for this is to setup the following mirror.
<mirror>
<id>people.apache.snapshots</id>
<url>http://people.apache.org/repo/m2-snapshot-repository</url>
<mirrorOf>apache.snapshots</mirrorOf>
</mirror>
> Remove all references to org.apache.maven:maven:2.04 - cvs.apache.org
> ---------------------------------------------------------------------
>
> Key: MNG-3713
> URL: http://jira.codehaus.org/browse/MNG-3713
> Project: Maven 2
> Issue Type: Bug
> Affects Versions: 2.0.5, 2.0.6, 2.0.7, 2.0.8, 2.0.9
> Reporter: Nathan Beyer (Cerner)
> Priority: Critical
>
> I don't know the complete picture, but here is what I do know.
> - maven-invoker-plugin + it tests pulls in maven-reporting-impl 2.0.4 during
> 'test:testCompile'
> - maven-reporting-impl 2.0.4 [1] has the parent maven-reporting 2.0.4
> - maven-reporting 2.0.4 [2] has the parent maven 2.0.4
> - maven 2.0.4 contains a repository with the ID, apache.snapshots, and URL,
> http://cvs.apache.org/maven-snapshot-repository
> - cvs.apache.org no longer exists
> The result of this is that every time a build with integration tests is run,
> there are multiple pauses like cvs.apache.org is looked up and times out.
> Though this happens consistently, the server is never mentioned for
> blacklisting.
> There are plenty of newer versions of maven-reporting, so it seems reasonable
> to just find these dependencies and upgrade them.
> [1]
> http://repo1.maven.org/maven2/org/apache/maven/reporting/maven-reporting-impl/2.0.4/maven-reporting-impl-2.0.4.pom
> [2]
> http://repo1.maven.org/maven2/org/apache/maven/reporting/maven-reporting/2.0.4/maven-reporting-2.0.4.pom
> [3] http://repo1.maven.org/maven2/org/apache/maven/maven/2.0.4/maven-2.0.4.pom
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
