RE: cvs commit: maven/src/bin maven maven.bat

2004-06-14 Thread Brett Porter
Right so we've both established that is works for maven (sh) inside cygwin and maven.bat inside cygwin. In maven.bat in cmd it will either be empty, or set to what the user has specified. The property is meant as a fallback for when user.home doesn't match $HOME, specifically for cygwin on windows

RE: cvs commit: maven/src/bin maven maven.bat

2004-06-14 Thread Jörg Schaible
Brett Porter wrote on Monday, June 14, 2004 3:25 PM: > Do you take issue with maven.bat or maven (the sh script)? > > It works on the shell script. HOME is a cygwin path, which I > convert to a windows path and pass in - but it remains a > shell path in the parent shell. This is something that C

RE: cvs commit: maven/src/bin maven maven.bat

2004-06-14 Thread Brett Porter
Do you take issue with maven.bat or maven (the sh script)? It works on the shell script. HOME is a cygwin path, which I convert to a windows path and pass in - but it remains a shell path in the parent shell. For the batch file - maybe it should be %USERDRIVE%%USERHOME%... Quoting Jörg Schaible

RE: cvs commit: maven/src/bin maven maven.bat

2004-06-14 Thread Jörg Schaible
Brett, I am not sure about this patch for the maven script. Despite a normal Windows shell, Cygwin defines a HOME of its own and it is one of its variables that are automatically converted into DOSish style starting a non-Cygwin app from a Cygwin shell. Did you test this ?? Regards, Jörg [EM