Maven Evangelism

Several projects have maven-metadata.xml files that are missing released versions

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Resolution: Fixed
  • Component/s: Invalid Metadata
  • Labels:
    None
  • Group ID:
    commons-httpclient
  • Artifact ID:
    commons-httpclient
  • Version:
    3.1-alpha1

Description

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.

Issue Links

is duplicated by

Bug - A problem which impairs or prevents the functions of the product. MEV-468 FindBugs metadata doesn't include 1.1.1 release

  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Bug - A problem which impairs or prevents the functions of the product. MNG-2555 maven-metadata.xml for springframework.spring is missing recent versions

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
is related to

Bug - A problem which impairs or prevents the functions of the product. MEV-565 commons-lang is missing versions greater then 2.1 in the metadata.

  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Patrick Moore added a comment -

This is a sample file showing what I think the maven-metadata.xml file should look like

Show
Patrick Moore added a comment - This is a sample file showing what I think the maven-metadata.xml file should look like
Hide
Permalink
Carlos Sanchez added a comment -

we're aware of these problems, hopefully will be solved with Archiva (or Maven Repository Manager)

Show
Carlos Sanchez added a comment - we're aware of these problems, hopefully will be solved with Archiva (or Maven Repository Manager)
Hide
Permalink
Nathan Beyer (Cerner) added a comment -

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?

Show
Nathan Beyer (Cerner) added a comment - 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?
Hide
Permalink
Henri Yandell added a comment -

Not soon I suspect - I think we should write a simple script that goes in and rewrites all the metadata files at our whim.

Alternatively, write a script to identify problems in the files, and then another to fix them.

Show
Henri Yandell added a comment - Not soon I suspect - I think we should write a simple script that goes in and rewrites all the metadata files at our whim. Alternatively, write a script to identify problems in the files, and then another to fix them.
Hide
Permalink
Noah Levitt added a comment -

Will this issue ever be fixed? Encountered it with hibernate, c3p0, commons-lang, ... like half the things I've tried.

Show
Noah Levitt added a comment - Will this issue ever be fixed? Encountered it with hibernate, c3p0, commons-lang, ... like half the things I've tried.
Hide
Permalink
Carlos Sanchez added a comment -

is not going to be resolved until somebody takes the time to write and automated way of updating the metadata

Show
Carlos Sanchez added a comment - is not going to be resolved until somebody takes the time to write and automated way of updating the metadata
Hide
Permalink
luke w patterson added a comment -

Any updates on this issue?

In general, who is responsible for maintaining metadata in central?

When I notice missing/incorrect metadata, where should I file a bug?

How should I respond to questions like these:
http://code.google.com/p/mockito/issues/detail?id=63#c2
?

I thought central was hosted with Nexus now. Is that correct? If so, how does that affect this issue?

Show
luke w patterson added a comment - Any updates on this issue? In general, who is responsible for maintaining metadata in central? When I notice missing/incorrect metadata, where should I file a bug? How should I respond to questions like these: http://code.google.com/p/mockito/issues/detail?id=63#c2 ? I thought central was hosted with Nexus now. Is that correct? If so, how does that affect this issue?
Hide
Permalink
Juven Xu added a comment -

hsqldb fixed

Show
Juven Xu added a comment - hsqldb fixed
Hide
Permalink
Juven Xu added a comment -

htmlunit fixed

Show
Juven Xu added a comment - htmlunit fixed
Hide
Permalink
Juven Xu added a comment -

fixed rhino/js

Show
Juven Xu added a comment - fixed rhino/js
Hide
Permalink
Juven Xu added a comment -

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

Show
Juven Xu added a comment - 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
Hide
Permalink
Antony Stubbs added a comment -

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.

Show
Antony Stubbs added a comment - 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.
Hide
Permalink
Juven Xu added a comment -

hi Antony,

This MEV project is no longer supported, please go to https://issues.sonatype.org/browse/MVNCENTRAL for maven central issues.

thanks,
Juven

Show
Juven Xu added a comment - hi Antony, This MEV project is no longer supported, please go to https://issues.sonatype.org/browse/MVNCENTRAL for maven central issues. thanks, Juven

People

  • Assignee:
    Juven Xu
    Reporter:
    Patrick Moore
Vote (9)
Watch (10)

Dates

  • Created:
    Updated:
    Resolved: