[SLING-9848] The ArtifactManager should handle SNAPSHOT dependencies exactly like Maven

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: Feature Model 1.2.10
• Component/s: Feature Model
• Assignee: Unassigned
• Reporter: Radu Cotescu
• Created: 22/Oct/20 14:03
• Updated: 01/Mar/21 15:13
• Resolved: 01/Mar/21 15:13

Description

When a feature provides a SNAPSHOT dependency by using the artifact's specific version generated by Nexus (e.g. 1.0.0-SNAPSHOT -> 1.0.0-20201021.121222-1), then the ArtifactManager fails to correctly find the dependency.

Assuming a definition like:

{
      "id":"org.myorg:mybundle:1.0.0-20201021.121222-1",
      "start-order":"20"
}

Maven would download / solve org/myorg/mybundle/1.0.0-SNAPSHOT/mybundle-1.0.0-20201021.121222-1.jar, whereas the ArtifactManager would try to download / solve
org/myorg/mybundle/1.0.0-20201021.121222-1/mybundle-1.0.0-20201021.121222-1.jar.

IMO, when working with Maven Repositories / Artifacts, the ArtifactManager should use Maven components for correctly resolving the artifacts the same way Maven would.