You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2007/01/24 12:16:26 UTC
[jira] Created: (MNG-2790) lastUpdated timestamp in local
repository metadata not updated on install if it already exists
lastUpdated timestamp in local repository metadata not updated on install if it already exists
----------------------------------------------------------------------------------------------
Key: MNG-2790
URL: http://jira.codehaus.org/browse/MNG-2790
Project: Maven 2
Issue Type: Bug
Components: Artifacts and Repositories
Affects Versions: 2.0.5
Reporter: Brett Porter
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)
--
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
[jira] Closed: (MNG-2790) lastUpdated timestamp in local repository
metadata not updated on install if it already exists
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed MNG-2790.
-----------------------------
Assignee: Brett Porter
Resolution: Fixed
Fix Version/s: 2.0.6
> lastUpdated timestamp in local repository metadata not updated on install if it already exists
> ----------------------------------------------------------------------------------------------
>
> Key: MNG-2790
> URL: http://jira.codehaus.org/browse/MNG-2790
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.5
> Reporter: Brett Porter
> Assigned To: Brett Porter
> Fix For: 2.0.6
>
>
> 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)
--
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
[jira] Updated: (MNG-2790) lastUpdated timestamp in local
repository metadata not updated on install if it already exists
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-2790:
------------------------------
Fix Version/s: (was: 2.0.6)
2.0.5
> lastUpdated timestamp in local repository metadata not updated on install if it already exists
> ----------------------------------------------------------------------------------------------
>
> Key: MNG-2790
> URL: http://jira.codehaus.org/browse/MNG-2790
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.5
> Reporter: Brett Porter
> Assigned To: Brett Porter
> Fix For: 2.0.5
>
>
> 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)
--
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