[
https://jira.codehaus.org/browse/MEV-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=281252#comment-281252
]
Antony Stubbs commented on MEV-443:
-----------------------------------
How is this issue "fixed"? IMO it shouldn't be marked fixed until all projects
are fixed and there's a fix in place to stop it happening again.
I've hit it with
<groupId>org.easytesting</groupId>
<artifactId>fest-assert</artifactId>
<version>[1.3]</version>
1.4 is missing from the meta data.
> Several projects have maven-metadata.xml files that are missing released
> versions
> ---------------------------------------------------------------------------------
>
> Key: MEV-443
> URL: https://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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
