[
https://issues.apache.org/jira/browse/MINVOKER-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17958264#comment-17958264
]
Olivier Lamy commented on MINVOKER-47:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-invoker-plugin#387|https://github.com/apache/maven-invoker-plugin/issues/387].
> Test builds fail to locate staged artifacts when using custom settings and
> non-default local repo path
> ------------------------------------------------------------------------------------------------------
>
> Key: MINVOKER-47
> URL: https://issues.apache.org/jira/browse/MINVOKER-47
> Project: Maven Invoker Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 1.2
> Reporter: Benjamin Bentmann
> Assignee: Benjamin Bentmann
> Priority: Minor
> Fix For: 1.3
>
>
> If the {{invoker:run}} goal
> - is configured to use a custom user settings file (as recommended for fast
> builds)
> - and no isolated local repo is to be used (not recommended but possible)
> - and the user has customized the location of his local repo
> the IT builds will fail.
> The {{invoker:install}} will properly stage the artifacts into the user's
> local repo but using a custom IT settings files (which doesn't specify a
> local repo path) will make Maven use the default local repo, which is empty.
> Hence, we should always specify the local repo path for the Maven invocation
> and not rely on Maven fetching it from the settings.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
