Hi Mirko,
This confirms why Karl Heinz had issues with the Maven Invoker 2.2 (take 1)
On Windows there's no issue, the mvn.bat/mvn.cmd always sets M2_HOME if
it's not there.
We could add an AssumeThat-clause in this test as well...
thanks,
Robert
Op Tue, 24 Mar 2015 22:16:59 +0100 schreef Mirko Friedenhagen
<mfriedenha...@apache.org>:
Hello,
I just checked out the trunk (r1643023) and running "mvn clean verify"
does not succeed neither with Maven 3.0.5, Maven 3.2.5 nor with Maven
3.3.1 (OS X 10.10.2, JDK 1.7.0_76):
The test
org.apache.maven.shared.release.exec.InvokerMavenExecutorTest#testEncryptSettings
is always failing with the following message from
/maven-invoker-2.1-sources.jar!/org/apache/maven/shared/invoker/MavenCommandLineBuilder.java:124
java.lang.IllegalStateException: Maven application directory was not
specified, and ${maven.home} is not provided in the system properties.
Please specify at least on of these.
When I set the M2_HOME variable on the command line manually, the tests
succeed.
Regards
Mirko
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
