[
http://jira.codehaus.org/browse/MNG-4326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4326.
----------------------------------
Resolution: Fixed
Fix Version/s: 3.0-alpha-8
Assignee: Benjamin Bentmann
Fixed in [r928842|http://svn.apache.org/viewvc?view=revision&revision=928842].
As long as the local copy satifies the update policy configured on a remote
repository, Maven will not fetch the remote repository's metadata.
> Maven should not check snapshot repositories for dependencies in the reactor
> ----------------------------------------------------------------------------
>
> Key: MNG-4326
> URL: http://jira.codehaus.org/browse/MNG-4326
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 2.0.10, 2.2.1
> Reporter: Paul Gier
> Assignee: Benjamin Bentmann
> Fix For: 3.0-alpha-8
>
>
> If I build a multi-module project with intermodule dependencies, Maven will
> still check the snapshot repository for module artifacts in order to update
> the metadata in the local repository. Maven should not check the snapshot
> repository for any artifacts that are currently in the reactor.
> In addition, if I install a snapshot artifact to the local repository, and
> then build another project that depends on the first project, Maven will
> check the snapshot repository. Instead, Maven should only check the snapshot
> repository when there is no up to date (according to the update policy) local
> artifact installation.
> This seems to be working normally in Maven 3.0-alpha-6, but still requires
> more testing.
--
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
