Hello there, I now have a workaround. I am setting:
<injectedMavenHome>${maven.home}</injectedMavenHome>
in maven-release-manager/pom.xml and use this to set:
releaseEnvironment.setMavenHome( new File( System.getProperty(
"injectedMavenHome" ) ) );
in the testcase.
Works fine from the command line.
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/
On Wed, Mar 25, 2015 at 10:04 PM, Bernd Eckenfels
<e...@zusammenkunft.net> wrote:
> Am Wed, 25 Mar 2015 21:01:53 +0100
> schrieb Mirko Friedenhagen <mfriedenha...@gmail.com>:
>> - however this will not help with IDEs like Eclipse or Intellij which
>> use their own code to invoke stuff.
>
> I guess it is better when you pass it as a system property:
>
> -Dmaven.home="${M2_HOME}"
>
> that way you dont need to export it and the configuration is consistent
> (with the settings the IDEs typically set as well).
>
> Gruss
> Bernd
>
> ---------------------------------------------------------------------
> 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
