[
http://jira.codehaus.org/browse/MENFORCER-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann moved MNG-4888 to MENFORCER-110:
--------------------------------------------------
Complexity: (was: Intermediate)
Component/s: (was: General)
Key: MENFORCER-110 (was: MNG-4888)
Project: Maven 2.x Enforcer Plugin (was: Maven 2 & 3)
> Enforcer 1.1-SNAPSHOT uses wrong maven-parent
> ---------------------------------------------
>
> Key: MENFORCER-110
> URL: http://jira.codehaus.org/browse/MENFORCER-110
> Project: Maven 2.x Enforcer Plugin
> Issue Type: Bug
> Reporter: Matthias Weßendorf
>
> The enforcer's trunk pom.xml:
> https://svn.apache.org/repos/asf/maven/enforcer/trunk/pom.xml
> is linked against maven-parent 17. I don't see the 17 'release'. Examples:
> https://repository.apache.org/content/repositories/releases/org/apache/maven/maven-parent/
> https://repository.apache.org/content/repositories/public/org/apache/maven/maven-parent/
> http://repo2.maven.org/maven2/org/apache/maven/maven-parent/
> However, there is only 17-SNAPSHOT:
> https://repository.apache.org/content/groups/snapshots/org/apache/maven/maven-parent/
> FWIW, it's trunk, however, is labeled as 18-SNAPSHOT:
> https://svn.apache.org/repos/asf/maven/pom/trunk/maven/pom.xml
> Looks like the 17 is missing...
--
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
