[
https://issues.apache.org/jira/browse/SLING-8905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16991787#comment-16991787
]
Carsten Ziegeler commented on SLING-8905:
-----------------------------------------
[~rombert] Agreed, let's fail if both scm-location and source-ids are specified
(we can add a check to the analyser as well)
Metadata is currently limited to values of type String, so a json structure
does not work. I guess the easiest is to stick with scm-location supporting a
single location for now
> Always use scm-location if defined
> ----------------------------------
>
> Key: SLING-8905
> URL: https://issues.apache.org/jira/browse/SLING-8905
> Project: Sling
> Issue Type: Improvement
> Components: Maven Plugins and Archetypes
> Reporter: Robert Munteanu
> Priority: Major
> Fix For: slingfeature-maven-plugin 1.1.12
>
>
> The behaviour of {{scm-location}} and {{source-ids}} is not consistent. The
> {{sourceId}} is always consulted, while the {{scm-location}} is used only if
> the regular sources checkout fails.
> This does not help when, for instance, an artifact A wraps artifact B and
> also provides a {{-sources}} jar. The {{ApisJarMojo}} will download the
> {{-sources}} jar and ignore the {{scm-location}} information, leading to
> sources not being found.
> I think that {{scm-location}} should always be used preferred to automatic
> download os the {{-sources}} jar, as it is effectively an override.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
