maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kenney Westerhof (JIRA)" <>
Subject [jira] Closed: (MNG-2712) update policy 'daily' not honored
Date Fri, 22 Dec 2006 19:05:41 GMT
     [ ]

Kenney Westerhof closed MNG-2712.

       Resolution: Fixed
    Fix Version/s: 2.1

Fixed in revision 489724.

Also updated unit test to test that the files ARE written, even if the metadata contains LATEST/RELEASE,
but without the version tag.

Ran integration tests on the core, and there don't seem to be any problems with this.

> update policy 'daily' not honored
> ---------------------------------
>                 Key: MNG-2712
>                 URL:
>             Project: Maven 2
>          Issue Type: Bug
>            Reporter: Kenney Westerhof
>         Assigned To: Kenney Westerhof
>             Fix For: 2.1
> under certain circumstances, the '<updatePolicy>daily</updatePolicy>' isn't
> This is the case where the remote metadata file doesn't exist, or contains <version>RELEASE/LATEST
(which should never happen)..
> The timestamp used to compare for the update is 0L, because the local file doesn't exist.
> Then the remote file is retrieved, which also doesn't exist, and no metadatafile is created.
> The next time an up2date check is done, again against timestamp 0 for a non-existent
> This means that if you define a custom snapshot repo in settings.xml or a pom, and you
have 500 transitive
> deps, the repo's that don't have that artifact are consulted 500 times for each mvn invocation.
> A build that normally takes about 20 seconds takes more than 10 minutes because of this

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message