You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Borut Bolcina (JIRA)" <ji...@codehaus.org> on 2009/10/20 15:14:26 UTC
[jira] Created: (MEV-639) log4j bad metadata
log4j bad metadata
------------------
Key: MEV-639
URL: http://jira.codehaus.org/browse/MEV-639
Project: Maven Evangelism
Issue Type: Bug
Components: Invalid Metadata
Reporter: Borut Bolcina
why there are no 1.2.14 and 1.2.15 versions in at
http://repo1.maven.org/maven2/log4j/log4j/maven-metadata.xml
<metadata>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
<version>1.1.3</version>
<versioning>
<versions>
<version>1.1.3</version>
<version>1.2.4</version>
<version>1.2.5</version>
<version>1.2.6</version>
<version>1.2.7</version>
<version>1.2.8</version>
<version>1.2.11</version>
<version>1.2.9</version>
<version>1.2.12</version>
<version>1.2.13</version>
</versions>
</versioning>
</metadata>
--
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-639) log4j bad metadata
Posted by "Jim At Company (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEV-639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206555#action_206555 ]
Jim At Company commented on MEV-639:
------------------------------------
Too bad this has not been addressed yet.
I don't know who's in charge of the maven metadata, but I just filed a similar bug at
https://issues.apache.org/bugzilla/show_bug.cgi?id=48527
I need this for hard and range dependencies.
> log4j bad metadata
> ------------------
>
> Key: MEV-639
> URL: http://jira.codehaus.org/browse/MEV-639
> Project: Maven Evangelism
> Issue Type: Bug
> Components: Invalid Metadata
> Reporter: Borut Bolcina
>
> why there are no 1.2.14 and 1.2.15 versions in at
> http://repo1.maven.org/maven2/log4j/log4j/maven-metadata.xml
> <metadata>
> <groupId>log4j</groupId>
> <artifactId>log4j</artifactId>
> <version>1.1.3</version>
> <versioning>
> <versions>
> <version>1.1.3</version>
> <version>1.2.4</version>
> <version>1.2.5</version>
> <version>1.2.6</version>
> <version>1.2.7</version>
> <version>1.2.8</version>
> <version>1.2.11</version>
> <version>1.2.9</version>
> <version>1.2.12</version>
> <version>1.2.13</version>
> </versions>
> </versioning>
> </metadata>
--
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-639) log4j bad metadata
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEV-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carlos Sanchez closed MEV-639.
------------------------------
Resolution: Fixed
Assignee: Carlos Sanchez
> log4j bad metadata
> ------------------
>
> Key: MEV-639
> URL: http://jira.codehaus.org/browse/MEV-639
> Project: Maven Evangelism
> Issue Type: Bug
> Components: Invalid Metadata
> Reporter: Borut Bolcina
> Assignee: Carlos Sanchez
>
> why there are no 1.2.14 and 1.2.15 versions in at
> http://repo1.maven.org/maven2/log4j/log4j/maven-metadata.xml
> <metadata>
> <groupId>log4j</groupId>
> <artifactId>log4j</artifactId>
> <version>1.1.3</version>
> <versioning>
> <versions>
> <version>1.1.3</version>
> <version>1.2.4</version>
> <version>1.2.5</version>
> <version>1.2.6</version>
> <version>1.2.7</version>
> <version>1.2.8</version>
> <version>1.2.11</version>
> <version>1.2.9</version>
> <version>1.2.12</version>
> <version>1.2.13</version>
> </versions>
> </versioning>
> </metadata>
--
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