[
http://jira.codehaus.org/browse/MNG-2989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated MNG-2989:
------------------------------
Fix Version/s: (was: Reviewed Pending Version Assignment)
2.0.x
> M2_HOME is incorrect when launched from another process
> -------------------------------------------------------
>
> Key: MNG-2989
> URL: http://jira.codehaus.org/browse/MNG-2989
> Project: Maven 2
> Issue Type: Improvement
> Components: Command Line
> Affects Versions: 2.0.6
> Environment: WinXP
> Reporter: Tim Reilly
> Priority: Minor
> Fix For: 2.0.x
>
>
> This is just an idea to solve the following: I believe echo'ing ~dp0 when
> launching maven.bat from ant exec produces the ant.bat processes ~0; not the
> maven bat files ~0 -since createProc API is used the processes command is
> the first argument.
> I think you may get around this by putting a new "finder file" .bat along
> side mvn.bat . Since mvn.bat and find_m2.bat are both on the path I can
> "discover" where M2_HOME is from the %PATH%.
> Within mvn.bat
> if "%m2_home%" == ""(
> if "%OS%"=="Windows_NT" (call find_m2.bat)
> )
> Within find_m2.bat:
> @echo off
> setlocal
> set _WHERE_IS_M2=%~dp0
> set M2_LOCAL_HOME=%__WHERE_IS_M2:\bin=%
> @REM echo %M2_LOCAL_HOME%
> endlocal & set M2_HOME=%M2_LOCAL_HOME%
--
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
