[
https://issues.apache.org/jira/browse/MSHARED-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17959200#comment-17959200
]
Matthias Bünger commented on MSHARED-72:
----------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-verifier#121|https://github.com/apache/maven-verifier/issues/121].
> Use current local repo for forked Maven invocations by default
> --------------------------------------------------------------
>
> Key: MSHARED-72
> URL: https://issues.apache.org/jira/browse/MSHARED-72
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-verifier
> Affects Versions: maven-verifier-1.0
> Reporter: Benjamin Bentmann
> Assignee: Benjamin Bentmann
> Priority: Major
> Fix For: maven-verifier-1.2
>
>
> The Verifier queries the property {{use.mavenRepoLocal}} to decide whether
> the current local repo path should be propagated to the forked Maven
> invocation. This property defaults currently to {{false}}, making the forked
> builds in principal use a different local repo than the parent build. This is
> usually not intended, imagine the parent build was run with {{-D
> maven.repo.local=<dir>}} to have all builds run in a (specially prepared)
> sandbox environment. To make the sub builds easily stay in the sandbox, the
> default value for {{use.mavenRepoLocal}} should be {{true}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
