svn commit: r696749 - /maven/shared/trunk/maven-verifier/src/main/java/org/apache/maven/it/Verifier.java

[be...@apache.org]

Author: bentmann
Date: Thu Sep 18 11:17:11 2008
New Revision: 696749

URL: http://svn.apache.org/viewvc?rev=696749&view=rev
Log:
[MSHARED-72] Use current local repo for forked Maven invocations by default

o Added rationale for further reference

Modified:
    maven/shared/trunk/maven-verifier/src/main/java/org/apache/maven/it/Verifier.java

Modified: maven/shared/trunk/maven-verifier/src/main/java/org/apache/maven/it/Verifier.java
URL: http://svn.apache.org/viewvc/maven/shared/trunk/maven-verifier/src/main/java/org/apache/maven/it/Verifier.java?rev=696749&r1=696748&r2=696749&view=diff
==============================================================================
--- maven/shared/trunk/maven-verifier/src/main/java/org/apache/maven/it/Verifier.java (original)
+++ maven/shared/trunk/maven-verifier/src/main/java/org/apache/maven/it/Verifier.java Thu Sep 18 11:17:11 2008
@@ -1006,6 +1006,12 @@
                 cli.createArgument().setLine( "-D" + key + "=" + systemProperties.getProperty( key ) );
             }
 
+            /*
+             * NOTE: Unless explicitly requested by the caller, the forked builds should use the current local
+             * repository. Otherwise, the forked builds would in principle leave the sandbox environment which has been
+             * setup for the current build. In particular, using "maven.repo.local" will make sure the forked builds use
+             * the same local repo as the parent build even if a custom user settings is provided.
+             */
             boolean useMavenRepoLocal =
                 Boolean.valueOf( verifierProperties.getProperty( "use.mavenRepoLocal", "true" ) ).booleanValue();