I seem to have it resolved now ... The wrapper invoked by 'run.bat' uses a 'wrapper.conf' file, where the wrapper.java.command is defined.
It was originally set to %JAVA_HOME%/bin/java My JAVA_HOME was (for the cygwin bash shell) set to /cygdrive/c/Program\ Files/Java/jdk1.5.0_07 The wrapper was unable to invoke the jvm using this command. I modified the 'wrapper.conf' file to explicitly set wrapper.java.command to C:\Program Files\Java\jdk1.5.0_07 Invoking 'run.bat' from within cygwin worked. [Oddly, I got the same failure mode when setting wrapper.java.command to '$JAVA_HOME/bin/java'.] Brad -----Original Message----- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 28, 2006 2:57 PM To: [email protected] Subject: Re: Shamefully Simple Question Check if JAVA_HOME is accessible in cygwin Emmanuel Brad Harper a écrit : > This is the most fundamentally newbie question possible ... > > I've just downloaded and unzipped Continuum 1.0.3 on a > Windows system. > > JAVA_HOME is set (to JDK 1.5.0_07). > > When I run bin/win32/run.bat (from Cygwin bash), I see > > wrapper | --> Wrapper Started as Console > wrapper | Launching a JVM... > wrapper | Unable to execute Java command. The system cannot \ > find the file specified. (0x2) > wrapper | "%JAVA_HOME%\bin\java" -Dclasswords.conf=... > wrapper | Critical error: wait for JVM process failed > Press any key to continue . . . > > No answer jumped out from the FAQ at maven.apache.org/continuum/ > or from the result of likely text searches on the continuum-users > list at mail-archive.com. > > I must be missing something blatantly obvious ... > > Brad > > > > > >
