[MNG-2994] Snapshot repositories are not checked when using ranges

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.6
• Fix Version/s: 3.0-beta-1
• Component/s: Artifacts and Repositories
• Environment: Windows XP, Cygwin
• Flags: Patch
• Assignee: Benjamin Bentmann
• Reporter: Mark Hobson
• Created: 18/May/07 11:20
• Updated: 08/Feb/20 15:41
• Resolved: 08/Apr/10 16:35

Description

The attached patch demonstrates the problem by adding it0121. If the test repository has releases enabled, the test passes, when they are disabled, the test fails. This appears to be due to DefaultArtifact.isSnapshot returning false for unresolved ranges, thus causing snapshot repositories to be disabled when resolving artifacts.

Issue Links

• depends upon: MNG-3092 Resolution of version ranges with non-snapshot bounds can resolve to a snapshot version
• is duplicated by: MNG-2525 SNAPSHOT dependencies aren't found when repository has 'release' disabled and a version range is used
• is duplicated by: MNG-4295 version ranges are not resolved from snapshot only repositories
• is related to: MRELEASE-177 generateReleasePoms does not work
• relates to: MNG-3376 plugin repositories are not checked when looking for snapshot plugin.