[
http://jira.codehaus.org/browse/MERCURY-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=168986#action_168986
]
Oleg Gusakov commented on MERCURY-103:
--------------------------------------
issue traced to several problems:
# stale data in the local repository: cache refers to a snapshot which is
already purged from the server
## repository updatePolicy is set to "always", but stale data still shows up
# there is a -SNAPSHOT jar and a couple of timestamps in the repository. And
SNAPSHOT happened to be a copy of an older timestamp, after which APIs has
changed
## old Mercury behavior - order timestamps, but choose -SNAPSHOT if one is
present
# lastModified on the stale SNAPSHOT jar is after the latest timestamp jar, so
even fixing the sequence, in which local snapshots are processed, we'll be
getting the wrong version
> Maven bootstrap fails on some local repos
> -----------------------------------------
>
> Key: MERCURY-103
> URL: http://jira.codehaus.org/browse/MERCURY-103
> Project: Mercury
> Issue Type: Bug
> Components: Ant tasks, Dependency Builder, Repository
> Affects Versions: 1.0-alpha-6
> Reporter: Oleg Gusakov
> Assignee: Oleg Gusakov
> Fix For: 1.0-alpha-6
>
> Attachments: bad-mercury-repo.zip
>
>
--
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
