Maven 2 & 3

[regression] RELEASE field of repository metadata is not updated upon repeated deployments

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 3.0.1
  • Fix Version/s: 3.0.2
  • Component/s: Artifacts and Repositories
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

As reported by Marcin Kuthan on the user list, the g:a-level metadata's release field is not updated upon redeployments, i.e. the value is stuck at its initial value.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Benjamin Bentmann added a comment -

Fixed in r1054683.

Show
Benjamin Bentmann added a comment - Fixed in r1054683 .
Hide
Permalink
Frank Prumbaum added a comment -

I can confirm the fix in 3.0.3.

What is still not updated is the LATEST-Tag.

Our problem with this is the Nexus-repository manager, because there the LATEST-Tag is inserted when you (re-)create maven metadata (v.1.9.0.1).

We deploy your software querying nexus with the v=LATEST parameter which takes into account the RELEASE and LATEST-Tag. If maven never updates LATEST but nexus does, we can never be sure what version will be deployed. What is sonatype's strategy on this type of metadata?

Show
Frank Prumbaum added a comment - I can confirm the fix in 3.0.3. What is still not updated is the LATEST-Tag. Our problem with this is the Nexus-repository manager, because there the LATEST-Tag is inserted when you (re-)create maven metadata (v.1.9.0.1). We deploy your software querying nexus with the v=LATEST parameter which takes into account the RELEASE and LATEST-Tag. If maven never updates LATEST but nexus does, we can never be sure what version will be deployed. What is sonatype's strategy on this type of metadata?
Hide
Permalink
Benjamin Bentmann added a comment -

LATEST is only ever used for plugins. This metaversion is an internal impl detail, ordinary dependency resolution should use version ranges.

Show
Benjamin Bentmann added a comment - LATEST is only ever used for plugins. This metaversion is an internal impl detail, ordinary dependency resolution should use version ranges.

People

  • Assignee:
    Benjamin Bentmann
    Reporter:
    Benjamin Bentmann
Vote (1)
Watch (3)

Dates

  • Created:
    Updated:
    Resolved: