You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Dennis Lundberg (JIRA)" <ji...@codehaus.org> on 2005/12/18 21:16:49 UTC

[jira] Commented: (MEV-264) commons-logging-1.1-dev is listed in maven-metadata, but no binary is found in the repository

    [ http://jira.codehaus.org/browse/MEV-264?page=comments#action_53669 ] 

Dennis Lundberg commented on MEV-264:
-------------------------------------

The binary was previously removed from the repo as it was published by mistake. So 1.1-dev should be removed from the metadata file.

> commons-logging-1.1-dev is listed in maven-metadata, but no binary is found in the repository
> ---------------------------------------------------------------------------------------------
>
>          Key: MEV-264
>          URL: http://jira.codehaus.org/browse/MEV-264
>      Project: Maven Evangelism
>         Type: Bug

>   Components: Invalid POM
>     Reporter: Arik Kfir

>
>
> The 'maven-metadata.xml' in commons-logging:commons-logging lists 1.1-dev version, but there's no JAR file there. 
> when a project defines a dependency on commons-logging with a range like "[1.0,)" (which means give me the newest), Maven fails since it recognizes that there's a 1.1-dev release, but can't find the binary for it. 
> Please post the 1.1-dev or remove it from maven-metadata.xml - thanks :)

-- 
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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org