maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Casey (JIRA)" <j...@codehaus.org>
Subject [jira] Closed: (MNG-3436) updateInterval checking for releases causes major slow-down
Date Wed, 05 Mar 2008 02:20:28 GMT

     [ http://jira.codehaus.org/browse/MNG-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

John Casey closed MNG-3436.
---------------------------

       Resolution: Fixed
    Fix Version/s: 2.1-alpha-1

fixed.

> updateInterval checking for releases causes major slow-down
> -----------------------------------------------------------
>
>                 Key: MNG-3436
>                 URL: http://jira.codehaus.org/browse/MNG-3436
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.1-alpha-1
>            Reporter: John Casey
>            Assignee: John Casey
>             Fix For: 2.1-alpha-1
>
>
> One change that crept into maven-artifact recently without my full understanding enabled
the updateInterval calculation for release artifacts. Since releases are considered immutable
by Maven, update-interval calculations should never cause released artifacts to be re-resolved.
> NOTE: This does NOT apply to release metadata, as the meta-versions RELEASE and LATEST
may change with successive releases to a particular project...release metadata should be checked
according to the updateInterval in the releases section of the repository definition.

-- 
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

        

Mime
View raw message