Maven 2 & 3

lastUpdated timestamp in local repository metadata not updated on install if it already exists

Details

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

Description

while this was always the case, it went unnoticed because the file timestamp was relied upon instead of the metadata timestamp (Which is now used in consideration, and is causing snapshots to be used from the remote repository even if it has been built locally)

Issue Links

is related to

Bug - A problem which impairs or prevents the functions of the product. MNG-1908 snapshots not deployed using m2, or deployed with uniqueVersion = false are not updated if present locally

  • Blocker - Blocks development and/or testing work, production could not run
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

There are no comments yet on this issue.

People

  • Assignee:
    Brett Porter
    Reporter:
    Brett Porter
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: