[
https://issues.apache.org/jira/browse/SLING-12932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18018418#comment-18018418
]
Robert Munteanu commented on SLING-12932:
-----------------------------------------
This is probably what we saw in INFRA-27035:
- local repository configured as sub-dir in Jenkins:
https://github.com/apache/sling-tooling-jenkins/blob/a9c7d5f999acb07c050e1ac0d824196ab3fcc1fc/vars/slingOsgiBundleBuild.groovy#L200
- sling feature launcher does not respect that setting and looks in
$HOME/.m2/repository
- sling feature launcher finds outdated SNAPSHOTS in $HOME/.m2/repository and
fails
> Explicitly configure the local maven repository when launching
> --------------------------------------------------------------
>
> Key: SLING-12932
> URL: https://issues.apache.org/jira/browse/SLING-12932
> Project: Sling
> Issue Type: Improvement
> Components: Maven Plugins and Archetypes
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Priority: Major
> Fix For: Feature Launcher Maven Plugin 0.1.10
>
>
> When starting a feature without any repository URLs configured the default
> ones are picked up from
> https://github.com/apache/sling-org-apache-sling-feature/blob/f8872f27ed626e169326a4f94b55f3059cd527f8/src/main/java/org/apache/sling/feature/io/artifacts/ArtifactManagerConfig.java#L77-L79
> , including detection of the Maven settings file -
> https://github.com/apache/sling-org-apache-sling-feature/blob/f8872f27ed626e169326a4f94b55f3059cd527f8/src/main/java/org/apache/sling/feature/io/artifacts/ArtifactManagerConfig.java#L203-L222
> .
> This is good enough for most cases. However, this cannot detect overrides set
> via the Maven invocation such as {{--settings}} and {{-Dmaven.repo.local}} .
> Therefore the plugin should explicitly set the artifact URLs to match the
> behaviour of the feature launcher, but consulting the actual settings
> reported by Maven.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
