FSchumacher commented on issue #5789:
URL: https://github.com/apache/jmeter/issues/5789#issuecomment-1528730937
> Ok, thanks but as usually it lacks some description, are these variables
changed just for start of Jmeter or permanently on the system? There could be
also problem with right, on some systems you can run jmeter.bat, but not some
custom *.bat because of security team ideas..
PRs for the documentation are always welcome, as we can't know, what is
missing for other readers.
The content of setenv.bat (or setenv.sh) is evaluated in the context of
jmeter.bat (or jmeter.sh) and it will not permanently set any values in your
system.
>
> I checked by Jmeter directory there is not setent.bat so im probably
supposed to create it? Maybe i have too old version, i checked 5.4.3
This mechanism was introduced with JMeter 4.0 (you can check
https://jmeter.apache.org/changes_history.html)
The idea is, that you create it yourself. That way any update of JMeter will
*not* overwrite your settings in that file.
>
> Add it to one place, to jmeter.bat would make more sense, because
Jmeter.bat is already Windows only.. more configs seems over engineered..
Because of the reason I gave above (overwriting your settings on update), it
is - in my opinion - a better place to put your settings, than to patch a file,
that comes with the distribution and will likely change with each update.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@jmeter.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
