maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bentmann (JIRA)" <>
Subject [jira] Closed: (MSHARED-72) Use current local repo for forked Maven invocations by default
Date Wed, 17 Sep 2008 15:28:48 GMT


Benjamin Bentmann closed MSHARED-72.

         Assignee: Benjamin Bentmann
       Resolution: Fixed
    Fix Version/s: maven-verifier 1.2

Done in [r696337|].

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


View raw message