[MNG-5366] [Regression] resolveAlways does not force dependency resolution in Maven 3.0.4

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.4, 3.0.5, 3.1.0, 3.1.1, 3.2.1, 3.2.2
• Fix Version/s: 3.2.5
• Component/s: Artifacts and Repositories
• Assignee: Unassigned
• Reporter: Paul Gier
• Created: 29/Oct/12 12:49
• Updated: 02/Jun/16 20:40
• Resolved: 02/Jun/16 20:40

Description

Using Maven 3.0.4, artifacts can only be resolved a single time during the build lifecycle using the Maven 2.x dependency resolution API. Using resolver.resolveAlways() should force re-resolution of the artifact, however if the artifact was already resolved once during the build, then it will not be re-resolved even when calling resolveAlways().

This works as expected in Maven 3.0.0-3.0.3, and the artifact is re-resolved.

Issue Links

• depends upon: MNG-5562 Upgrade Aether 1.0 when available
• relates to: MDEP-405 purge-local-repository on multi-module project results in failure