Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0.5, 3.0
-
Fix Version/s: 2.0.5
-
Component/s: None
-
Labels:None
-
Complexity:Intermediate
-
Number of attachments :
Description
under certain circumstances, the '<updatePolicy>daily</updatePolicy>' isn't honored.
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 file.
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 bug.
Issue Links
| This issue is duplicated by: | ||||
| MNG-2773 | Plugin repositories are chekced for SNAPSHOTS on every run in the 2.0.5 candidate |
|
|
|
| This issue relates to: | ||||
| MNG-3415 | Transfer errors cause junk metadata in the local repo |
|
|
|
| This issue depends upon: | ||||
| MNG-1320 | Build failed due to an empty or corrupt metadata file in the repository |
|
|
|
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.