Ok for me in Windows 10 with apache-jmeter-r1840238 .bat and cmd tested Le ven. 7 sept. 2018 à 06:30, Felix Schumacher < [email protected]> a écrit :
> Fixes went into trunk with r1840236. > > It would be great, if you could retest it. > > Felix > > Am 6. September 2018 11:25:10 MESZ schrieb Jmeter Tea <[email protected] > >: > >Hi > > > >The fix in jmeterw.cmd fix both options > > > >FYI > > > >On Thu, Sep 6, 2018 at 12:11 PM, Antonio Gomes Rodrigues > ><[email protected]> > >wrote: > > > >> If a use jmeterw.cmd without modification, it's doesn't works > >> > >> jmeter.bat wotks fine > >> > >> If I change "Apache JMeter" to "Apache_JMeter" in jmeterw.cmd, now > >> jmeterw.cmd works > >> > >> Antonio > >> > >> Le jeu. 6 sept. 2018 à 10:28, Felix Schumacher < > >> [email protected]> a écrit : > >> > >> > Am 06.09.2018 10:05, schrieb Antonio Gomes Rodrigues: > >> > > Hi, > >> > > > >> > > Tested with apache-jmeter-r1840164 in a windows 10 and it's works > >fine > >> > > > >> > > Can you give us more information (windows release...) > >> > > >> > I tested it here on windows 7 and it gave the same error message. > >It > >> > seems the cmd shell doesn't like a variable with spaces inside > >quotes. > >> > My workaround was to change "Apache JMeter" to "Apache_JMeter". > >> > > >> > Could both of you test if after those changes (in jmeter.cmd and > >> > jmeterw.cmd) the start script still work? > >> > > >> > Thanks, > >> > Felix (who doesn't like windows batch scripts, especially their > >> > handling of spaces and quotes :) > >> > > >> > > > >> > > Le jeu. 6 sept. 2018 à 07:59, Jmeter Tea <[email protected]> a > >écrit > >> > > : > >> > > > >> > >> Hello, > >> > >> > >> > >> jmeter.bat ot jmeterw stop working on nightly build, error in > >console > >> > >> : > >> > >> JMeter"" was unexpected at this time. > >> > >> > >> > >> I suspect the following change is relevant: > >> > >> if "%JM_START%" == "start" ( > >> > >> set JM_START=start "Apache JMeter" > >> > >> ) > >> > >> > >> > >> FYI > >> > >> > >> > > >> >
