Use current local repo for forked Maven invocations by default --------------------------------------------------------------
Key: MSHARED-72 URL: http://jira.codehaus.org/browse/MSHARED-72 Project: Maven Shared Components Issue Type: Improvement Components: maven-verifier Affects Versions: maven-verifier 1.0 Reporter: Benjamin Bentmann 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 is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira