[ http://jira.codehaus.org/browse/MEV-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann moved MNG-4519 to MEV-651: -------------------------------------------- Version: 4.5+ Artifact ID: junit Complexity: (was: Intermediate) Component/s: (was: Artifacts and Repositories) Invalid Metadata Priority: (was: Major) Group ID: junit Workflow: jira (was: Maven New) Key: MEV-651 (was: MNG-4519) Project: Maven Evangelism (was: Maven 2 & 3) > Maven Junit's maven-metadata.xml is missing new versions > -------------------------------------------------------- > > Key: MEV-651 > URL: http://jira.codehaus.org/browse/MEV-651 > Project: Maven Evangelism > Issue Type: Bug > Components: Invalid Metadata > Reporter: Jane Young > > Not sure if this bug belongs here... > Take a look at http://repo1.maven.org/maven2/junit/junit/ and you'll see > versions 4.5, 4.6 and 4.7. > But if you look at > http://repo1.maven.org/maven2/junit/junit/maven-metadata.xml it stops at > version 4.4. > If I use version range (e.g. "[4.4,)") or the key word "RELEASE" in the pom > file, Maven downloads the highest version in maven-metadata.xml file and in > this case version 4.4 but the highest version in > http://repo1.maven.org/maven2/junit/junit is 4.7. > This is clearly an issue in maven-metadata.xml. However, is there a way for > Maven to find the latest version w/o relying on metadata.xml? > Also how can this be fixed in the Maven central repository? -- 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