[
https://issues.apache.org/jira/browse/SLING-9848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17219461#comment-17219461
]
Carsten Ziegeler commented on SLING-9848:
-----------------------------------------
Is this a problem of the ArtifactManager or ArtifactId.toMvnPath() ?
In any case, we need to detect that the provided version is a snapshot version
based on the format of the qualifier. It would be good if we could follow some
official maven procedure for detecting such
> 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)
