You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2010/04/09 15:39:23 UTC
[jira] Closed: (MNG-1751) merging metadata doesn't fail when
timestamp is in the future
[ http://jira.codehaus.org/browse/MNG-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MNG-1751.
----------------------------------
Resolution: Fixed
Assignee: Benjamin Bentmann
Fixed in [r932406|http://svn.apache.org/viewvc?view=revision&revision=932406].
Maven now issues a warning about the future timestamp and gracefully updates the metadata by fixing the timestamp.
> merging metadata doesn't fail when timestamp is in the future
> -------------------------------------------------------------
>
> Key: MNG-1751
> URL: http://jira.codehaus.org/browse/MNG-1751
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
> Reporter: Brett Porter
> Assignee: Benjamin Bentmann
> Fix For: 3.0-beta-1
>
>
> 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.
--
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