[jira] [Resolved] (SLING-8905) Always use scm-location if defined

["Robert Munteanu (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-8905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Munteanu resolved SLING-8905.
------------------------------------
    Resolution: Fixed

> 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
>            Assignee: Robert Munteanu
>            Priority: Major
>             Fix For: slingfeature-maven-plugin 1.1.12
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> 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)