[
https://issues.apache.org/jira/browse/SLING-9848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17219629#comment-17219629
]
Radu Cotescu commented on SLING-9848:
-------------------------------------
I didn't debug the code, so I'm not sure if the issue is in the
{{ArtifactManager}} or in the {{ArtifactId#toMvnPath}} implementation, though
somehow I suspect the former. The question is, couldn't we delegate to Eclipse
Aether for any Maven repository call? I know we'd add a dependency to the Sling
Feature code, but we'd rely on the exact same code Maven is using.
> 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
> Priority: Major
>
> 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)
