https://bz.apache.org/bugzilla/show_bug.cgi?id=62107
Felix Schumacher changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRME
https://bz.apache.org/bugzilla/show_bug.cgi?id=62107
moh.riza changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://bz.apache.org/bugzilla/show_bug.cgi?id=62107
--- Comment #29 from Felix Schumacher ---
Date: Thu Sep 6 17:00:22 2018
New Revision: 1840236
URL: http://svn.apache.org/viewvc?rev=1840236&view=rev
Log:
Spaces and quotes will confuse windows batch files
As reported on the mailing list the
https://bz.apache.org/bugzilla/show_bug.cgi?id=62107
Philippe Mouawad changed:
What|Removed |Added
Keywords||FixedInTrunk
Target Milestone|---
https://bz.apache.org/bugzilla/show_bug.cgi?id=62107
Felix Schumacher changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://bz.apache.org/bugzilla/show_bug.cgi?id=62107
--- Comment #27 from Felix Schumacher ---
Seems like we have to adapt the description of add a special case of start is
used without a title.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bz.apache.org/bugzilla/show_bug.cgi?id=62107
--- Comment #26 from logo...@gmx.at ---
In jmeter.bat it's described like this:
rem JM_START- set this to "start" to launch JMeter in a separate window
rem this is used by the jmeterw.cmd script.
But in jmeterw.cmd it's u
https://bz.apache.org/bugzilla/show_bug.cgi?id=62107
--- Comment #25 from Felix Schumacher ---
The variable JM_START must be 'start "empty or title"'. For n exsample look at
jmeter.bat.
If you know of a better solution for this bug, you are welcomed to produce a
patch :)
--
You are receiving t
https://bz.apache.org/bugzilla/show_bug.cgi?id=62107
logo...@gmx.at changed:
What|Removed |Added
Status|NEEDINFO|NEW
--- Comment #24 from logo...@gmx.a
https://bz.apache.org/bugzilla/show_bug.cgi?id=62107
--- Comment #23 from Manu ---
(In reply to Felix Schumacher from comment #22)
> The variable JM_LAUNCH has to point to a valid executable. So either a PATH
> relative name or an absolute name is OK.
>
> Is the current trunk bat working for you
https://bz.apache.org/bugzilla/show_bug.cgi?id=62107
--- Comment #22 from Felix Schumacher ---
The variable JM_LAUNCH has to point to a valid executable. So either a PATH
relative name or an absolute name is OK.
Is the current trunk bat working for you with environment variable (and with
'set "J
https://bz.apache.org/bugzilla/show_bug.cgi?id=62107
--- Comment #21 from Manu ---
(In reply to Felix Schumacher from comment #20)
> It is really strange that the string java is missing if you use the
> environment variable. Can you double check that it is really part of your
> environment variab
https://bz.apache.org/bugzilla/show_bug.cgi?id=62107
--- Comment #20 from Felix Schumacher ---
It is really strange that the string java is missing if you use the environment
variable. Can you double check that it is really part of your environment
variable?
--
You are receiving this mail becau
https://bz.apache.org/bugzilla/show_bug.cgi?id=62107
--- Comment #19 from Manu ---
(In reply to Felix Schumacher from comment #18)
> The changes are made in trunk, please try
> http://svn.apache.org/viewvc/jmeter/trunk/bin/jmeter.bat?view=log
I was testing with your fixes available in trunk and
https://bz.apache.org/bugzilla/show_bug.cgi?id=62107
--- Comment #18 from Felix Schumacher ---
The changes are made in trunk, please try
http://svn.apache.org/viewvc/jmeter/trunk/bin/jmeter.bat?view=log
--
You are receiving this mail because:
You are the assignee for the bug.
https://bz.apache.org/bugzilla/show_bug.cgi?id=62107
--- Comment #17 from Manu ---
(In reply to Felix Schumacher from comment #16)
> Is the current version from subversion working for you, when you use the
> environment variable?
When I use environment variable with setenv.bat it's working.
When
https://bz.apache.org/bugzilla/show_bug.cgi?id=62107
--- Comment #16 from Felix Schumacher ---
Is the current version from subversion working for you, when you use the
environment variable?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bz.apache.org/bugzilla/show_bug.cgi?id=62107
--- Comment #15 from Manu ---
(In reply to Felix Schumacher from comment #14)
> (In reply to Manu from comment #12)
> > (In reply to Felix Schumacher from comment #10)
> > > I have tested this (and the ones before) with the following setup:
> >
https://bz.apache.org/bugzilla/show_bug.cgi?id=62107
--- Comment #14 from Felix Schumacher ---
(In reply to Manu from comment #12)
> (In reply to Felix Schumacher from comment #10)
> > I have tested this (and the ones before) with the following setup:
> >
> > > set "JM_LAUNCH=C:\PATH WITH SPACES
https://bz.apache.org/bugzilla/show_bug.cgi?id=62107
--- Comment #13 from Manu ---
(In reply to Antonio Gomes Rodrigues from comment #8)
> Hi,
>
> Have you try with release 4.0 of JMeter?
>
> In my Windows machine (Windows 10), I have no problem
>
> Antonio
Actually first I tried with 4.0 ver
https://bz.apache.org/bugzilla/show_bug.cgi?id=62107
--- Comment #12 from Manu ---
(In reply to Felix Schumacher from comment #10)
> I have tested this (and the ones before) with the following setup:
>
> > set "JM_LAUNCH=C:\PATH WITH SPACES\java"
> > jmeter.bat
>
> Date: Mon Feb 19 18:13:45 201
https://bz.apache.org/bugzilla/show_bug.cgi?id=62107
--- Comment #11 from Manu ---
(In reply to Felix Schumacher from comment #9)
> The question for me is: how do you set JM_LAUNCH?
In the Environment variables >> user/system variables.
JM_LAUNCH = C:\Program Files\Java\jdk1.8.0_162\bin\
--
Y
https://bz.apache.org/bugzilla/show_bug.cgi?id=62107
--- Comment #10 from Felix Schumacher ---
I have tested this (and the ones before) with the following setup:
> set "JM_LAUNCH=C:\PATH WITH SPACES\java"
> jmeter.bat
Date: Mon Feb 19 18:13:45 2018
New Revision: 1824800
URL: http://svn.apache.
https://bz.apache.org/bugzilla/show_bug.cgi?id=62107
--- Comment #9 from Felix Schumacher ---
The question for me is: how do you set JM_LAUNCH?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bz.apache.org/bugzilla/show_bug.cgi?id=62107
--- Comment #8 from Antonio Gomes Rodrigues ---
Hi,
Have you try with release 4.0 of JMeter?
In my Windows machine (Windows 10), I have no problem
Antonio
--
You are receiving this mail because:
You are the assignee for the bug.
https://bz.apache.org/bugzilla/show_bug.cgi?id=62107
--- Comment #7 from Manu ---
(In reply to Felix Schumacher from comment #5)
> Next try to fix this. Can you try this one, too?
>
> Date: Sat Feb 17 13:34:28 2018
> New Revision: 1824588
>
> URL: http://svn.apache.org/viewvc?rev=1824588&view=r
https://bz.apache.org/bugzilla/show_bug.cgi?id=62107
--- Comment #6 from Manu ---
Able to reproduce the issue with the latest fix as well.
c:\apache-jmeter-3.2\bin>jmeter
'C:\Program' is not recognized as an internal or external command,
operable program or batch file.
errorlevel=9009
Press any
https://bz.apache.org/bugzilla/show_bug.cgi?id=62107
--- Comment #5 from Felix Schumacher ---
Next try to fix this. Can you try this one, too?
Date: Sat Feb 17 13:34:28 2018
New Revision: 1824588
URL: http://svn.apache.org/viewvc?rev=1824588&view=rev
Log:
Put JM_LAUNCH in front, if no JM_START
https://bz.apache.org/bugzilla/show_bug.cgi?id=62107
--- Comment #4 from Manu ---
c:\apache-jmeter-3.2\bin>jmeter.bat
c:\apache-jmeter-3.2\bin>rem Licensed to the Apache Software Foundation (ASF)
under one or more
c:\apache-jmeter-3.2\bin>rem contributor license agreements. See the NOTICE
https://bz.apache.org/bugzilla/show_bug.cgi?id=62107
--- Comment #3 from Manu ---
I took the jmeter.bat from the corresponding svn location and tried. It results
in below error.
"'C:\Program' is not recognized as an internal or external command,
operable program or batch file.
errorlevel=9009
Pre
https://bz.apache.org/bugzilla/show_bug.cgi?id=62107
Felix Schumacher changed:
What|Removed |Added
Status|NEW |NEEDINFO
OS|
https://bz.apache.org/bugzilla/show_bug.cgi?id=62107
--- Comment #1 from Felix Schumacher ---
*** Bug 62106 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are the assignee for the bug.
32 matches
Mail list logo