Maven 2 & 3

merging metadata doesn't fail when timestamp is in the future

Details

  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

on deploying, the timestamp got set to the future (set to GMT - Guelph Mean Time instead of the expected Grenwich

subsequent attempts to deploy reported success, but did not update the metadata.

The fact that we might suffer clock skew is probably a separate issue to consider, that might be reoslved through passing deployments via repoman.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Brett Porter added a comment -

Still an issue in 3.0-SNAPSHOT

Show
Brett Porter added a comment - Still an issue in 3.0-SNAPSHOT
Hide
Permalink
Benjamin Bentmann added a comment -

Fixed in r932406.

Maven now issues a warning about the future timestamp and gracefully updates the metadata by fixing the timestamp.

Show
Benjamin Bentmann added a comment - Fixed in r932406 . Maven now issues a warning about the future timestamp and gracefully updates the metadata by fixing the timestamp.

People

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

Dates

  • Created:
    Updated:
    Resolved: