[
http://jira.codehaus.org/browse/MEV-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell updated MEV-441:
------------------------------
Component/s: Metadata file
> Several projects have bad maven-metadata.xml files that are screwing up
> dependencies with version range feature
> ---------------------------------------------------------------------------------------------------------------
>
> Key: MEV-441
> URL: http://jira.codehaus.org/browse/MEV-441
> Project: Maven Evangelism
> Issue Type: Bug
> Components: Metadata file
> Reporter: Patrick Moore
>
> 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 in 2 ways.
> 1) maven-metadata.xml in the commons-httpclient directory does not list
> version 3.1-alpha1. This means that it will not find that version.
> 2) maven-metadata.xml lists a "<version>20020423</version>" which is
> numerically the highest number version, so my build is picking up this very
> old version.
> Other projects with this problem include: commons-chain and jmock.
--
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
