J�rg, I would think the same but I encountered some wierd behavoir. Part of it has to do with Cygwin shell variable expansion and part of it with the fact that when on Cygwin/Windows java expects the -jar value to be in the Windows path style. This fixed the problem for me because I forced the -jar value to be in the Windows path format.
When I ran the merlin.sh the java.exe program could not find the jar file with the main class to run. There is some other logic problem in the script I think that does not correctly set the variables in this file when dealing with Cygwin. That's why this change which should not have an effect is causing it to work properly on Cygwin. If I had the time I would rewrite the script altogether. If you would like to submit a new script or delta's I'll commit the changes. Alex > > From: J�rg Schaible <[EMAIL PROTECTED]> > Date: 2003/12/23 Tue AM 08:19:23 EST > To: [EMAIL PROTECTED] > Subject: Re: release loose ends on Cygwin shell env > > Hi Alex, > > Alex Karasulu wrote: > > The line I added was: > > > > MERLIN_BOOTSTRAP_JAR=$MERLIN_HOME'\'bin'\'lib'\'merlin-cli-3.2.jar > > > > you probably can see this from the committed update diff > > from the cvs mail sent out anyway.��But�let�me�know�if > > this fixes the cygwin problem with this script or not.��It > > did so for me. > > Hi Alex, > > this is not necessary if you assemble the value of the var after converting > MERLIN_HOME. > > Regards, > J�rg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
