[
http://jira.codehaus.org/browse/MNG-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom Parker reopened MNG-3035:
-----------------------------
Updated with example and further information (see previous comment)
> Maven caches missing snapshot dependencies, so further builds fail without
> checking the repo until the cache expires or -U is included to flush the cache
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MNG-3035
> URL: http://jira.codehaus.org/browse/MNG-3035
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.5
> Reporter: Tom Parker
> Priority: Minor
> Attachments: MNG-3035.zip
>
>
> The problem is caused by a slightly obscure sequence, in this example, I use
> two projects, Server & Common. Server depends on Common:
> Alice updates Server to depend on Common-1.2-SNAPSHOT instead of 1.1-SNAPSHOT
> and commits that change.
> Bob syncs that change and attempts a build of Server, maven checks for
> Common-1.2-SNAPSHOT in the local repo, finds it missing and checks the global
> repo, where it is also missing. Maven records this information in a cache and
> fails the build.
> Alice deploys Common-1.2-SNAPSHOT to the global repo.
> Bob attempts to build Server again, maven checks it's cached information and
> finds that Common-1.2-SNAPSHOT wasn't in the global repo last time, so fails
> the build.
> Maven should not fail the build due to missing dependencies simply because
> the cache says the dependency was missing last time. It should check the
> configured repos before failing.
--
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
