[MNG-4326] Maven should not check snapshot repositories for dependencies in the reactor

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.10, 2.2.1
• Fix Version/s: 3.0-beta-1
• Component/s: Dependencies
• Assignee: Benjamin Bentmann
• Reporter: Paul Gier
• Created: 26/Aug/09 17:12
• Updated: 07/Feb/11 15:30
• Resolved: 29/Mar/10 12:31

Description

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.

Issue Links

• is duplicated by: MNG-5004 updatePolicy="never" always does 1 initial check
• relates to: MNG-4755 Version ranges cannot be resolved against mirror if a local artifact is present