[
http://jira.codehaus.org/browse/MEV-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann moved MANTRUN-113 to MEV-627:
-----------------------------------------------
Priority: (was: Major)
Group ID: org.apache.ant
Environment: (was: Maven 2.0.9)
Affects Version/s: (was: 1.3)
Artifact ID: ant-junit
Version: 1.7.1
Workflow: jira (was: Maven New)
Key: MEV-627 (was: MANTRUN-113)
Project: Maven Evangelism (was: Maven 2.x Antrun Plugin)
> The dependent org/apache/ant/ant-junit/maven-metadata.xml does not list
> version 1.7.1 (required by this plugin)
> ---------------------------------------------------------------------------------------------------------------
>
> Key: MEV-627
> URL: http://jira.codehaus.org/browse/MEV-627
> Project: Maven Evangelism
> Issue Type: Bug
> Components: Invalid Metadata
> Reporter: Ken Lim
>
> In order to minimize variables in our build environment, we use <version>
> ranges by enclosing version numbers in brackets (eg.
> <version>[1.7.1]</version>).
> It looks like the
> http://download.java.net/maven/2/org/apache/ant/ant-junit/maven-metadata.xml
> file only has version 1.7.0 listed but version 1.7.1 artifacts are in the
> "ant-junit" directory.
> Can you please include version 1.7.1 in the maven-metadata.xml file?
--
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
