You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Radu Cotescu (Jira)" <ji...@apache.org> on 2020/10/22 14:04:00 UTC

[jira] [Created] (SLING-9848) The ArtifactManager should handle SNAPSHOT dependencies exactly like Maven

Radu Cotescu created SLING-9848:
-----------------------------------

             Summary: The ArtifactManager should handle SNAPSHOT dependencies exactly like Maven
                 Key: SLING-9848
                 URL: https://issues.apache.org/jira/browse/SLING-9848
             Project: Sling
          Issue Type: Improvement
          Components: Feature Model
    Affects Versions: Feature Model 1.2.10
            Reporter: Radu Cotescu


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:
{code}
{
      "id":"org.myorg:mybundle:1.0.0-20201021.121222-1",
      "start-order":"20"
}
{code}

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.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)