You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Juven Xu (JIRA)" <ji...@codehaus.org> on 2010/10/19 16:18:33 UTC
[jira] Closed: (MEV-443) Several projects have maven-metadata.xml
files that are missing released versions
[ http://jira.codehaus.org/browse/MEV-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Juven Xu closed MEV-443.
------------------------
Resolution: Fixed
Assignee: Juven Xu
I can not fix other commons stuff because there are rsync running from apache
see: https://issues.sonatype.org/browse/MVNCENTRAL-2
only after those projects migrate to repository.apache.org can we fix that
> Several projects have maven-metadata.xml files that are missing released versions
> ---------------------------------------------------------------------------------
>
> Key: MEV-443
> URL: http://jira.codehaus.org/browse/MEV-443
> Project: Maven Evangelism
> Issue Type: Bug
> Components: Invalid Metadata
> Reporter: Patrick Moore
> Assignee: Juven Xu
> Attachments: maven-metadata.xml
>
>
> I am trying to use the version range feature that is talked about in Better builds with Maven. I am specifying the commons-httpclient dependency as
> <dependency>
> <groupId>commons-httpclient</groupId>
> <artifactId>commons-httpclient</artifactId>
> <version>[3.1-alpha1,)</version>
> </dependency>
> Unfortunately, the usefulness of this feature is being sabotaged because the latest version of artificat is not listed in the maven-metadata.xml.
> Please update the maven-metadata.xml in this project and others. In particular
> hsqldb,
> commons-*,
> rhino/js
> htmlunit
> When updating those files, please do not list the versions using dates as their version id as it screws up the maven feature that allows dependencies to specify a version range.
--
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