Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Cannot Reproduce
-
Affects Version/s: 2.0.6
-
Fix Version/s: None
-
Component/s: Command Line
-
Labels:None
-
Environment:WinXP
-
Complexity:Intermediate
Description
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%
Issue Links
- is related to
-
MNG-2178
incorrect M2_HOME guess in mvn.bat
-
<target name="help">
<exec executable="cmd">
<arg value="/c"/>
<arg value="mvn.bat"/>
<arg value="-v"/>
</exec>
</target>
Works for me without M2_HOME set.