You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2006/05/24 20:23:11 UTC
[jira] Updated: (MNG-1751) merging metadata doesn't fail when
timestamp is in the future
[ http://jira.codehaus.org/browse/MNG-1751?page=all ]
John Casey updated MNG-1751:
----------------------------
Fix Version: (was: 2.0.5)
> 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
> Type: Bug
> Components: Artifacts and Repositories
> Reporter: Brett Porter
>
>
> 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