[ http://jira.codehaus.org/browse/MEV-443?page=comments#action_81727 ] Nathan Beyer (Cerner) commented on MEV-443: -------------------------------------------
What's a pragmatic time frame for Archiva being used by the central repo and having these issues resolved? The last comment on this issue was 3 months ago. Is it still practical to postpone these metadata fixes? What can the community do to help? If we posted updated metadata files, could these be uploaded? What can we do to push Archiva over the line? > 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 > Reporter: Patrick Moore > 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
