You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Ken Lim (JIRA)" <ji...@codehaus.org> on 2009/07/09 02:48:23 UTC
[jira] Created: (MANTRUN-113) The dependent
org/apache/ant/ant-junit/maven-metadata.xml does not list version 1.7.1
(required by this plugin)
The dependent org/apache/ant/ant-junit/maven-metadata.xml does not list version 1.7.1 (required by this plugin)
---------------------------------------------------------------------------------------------------------------
Key: MANTRUN-113
URL: http://jira.codehaus.org/browse/MANTRUN-113
Project: Maven 2.x Antrun Plugin
Issue Type: Bug
Affects Versions: 1.3
Environment: Maven 2.0.9
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
[jira] Commented: (MEV-627) The dependent
org/apache/ant/ant-junit/maven-metadata.xml does not list version 1.7.1
(required by this plugin)
Posted by "Ken Lim (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEV-627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183961#action_183961 ]
Ken Lim commented on MEV-627:
-----------------------------
I apologize for the cut&paste error. The 1.7.1 version is missing from the central repo, not the previously-mentioned download.java.net repo.
Here is the correct URL to the metadata file that is missing the 1.7.1 version:
http://repo1.maven.org/maven2/org/apache/ant/ant-junit/maven-metadata.xml
> 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
[jira] Updated: (MEV-627) The dependent
org/apache/ant/ant-junit/maven-metadata.xml does not list version 1.7.1
(required by this plugin)
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEV-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann updated MEV-627:
----------------------------------
Component/s: Invalid Metadata
> 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
[jira] Moved: (MEV-627) The dependent
org/apache/ant/ant-junit/maven-metadata.xml does not list version 1.7.1
(required by this plugin)
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Closed: (MEV-627) The dependent
org/apache/ant/ant-junit/maven-metadata.xml does not list version 1.7.1
(required by this plugin)
Posted by "Juven Xu (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEV-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Juven Xu closed MEV-627.
------------------------
Resolution: Fixed
Assignee: Juven Xu
maven-metadata.xml is fixed
> 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
> Assignee: Juven Xu
>
> 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