Improve command line scripts

[tilln]

• Change to latest cmdrunner.jar version
• Add JVM_ARGS environment variable to java command to be more consistent with JMeter

The latter allows for e.g. easier timezone changes for over time visualizers etc.

[undera]

PR mentions "Change to latest cmdrunner.jar version", but I don't see any changes related to that.
What do I miss?

[tilln]

PR mentions "Change to latest cmdrunner.jar version", but I don't see any changes related to that. What do I miss?

Oh I now see that I've missed the change in the repo descriptor which has still

"cmdrunner>=2.2": "https://search.maven.org/remotecontent?filepath=kg/apc/cmdrunner/2.2/cmdrunner-2.2.jar"

Question would be whether this needs a new release/version number of the tools like jpgc-cmd, jpgc-filterresults and jpgc-plancheck, or just a new entry with the same jar version but updated cmdrunner, e.g.

      "2.3": {
        "changes": "Use latest cmdrunner version",
        "downloadUrl": "https://search.maven.org/remotecontent?filepath=kg/apc/jmeter-plugins-cmd/2.2/jmeter-plugins-cmd-2.2.jar",
        "libs": {
          "jmeter-plugins-cmn-jmeter>=0.7": "https://search.maven.org/remotecontent?filepath=kg/apc/jmeter-plugins-cmn-jmeter/0.7/jmeter-plugins-cmn-jmeter-0.7.jar",
          "cmdrunner>=2.3": "https://search.maven.org/remotecontent?filepath=kg/apc/cmdrunner/2.3/cmdrunner-2.3.jar"
        }
      }

[undera]

I'm getting old...

[tilln]

I'm getting old...

Me too. :`(

Looks like the merge published the wiki which now mentions the env var despite the feature not being released yet.

Do we want to fix this or rather push out new releases for the tools?

[undera]

If the motion is to release new version - that should be done

[tilln]

If the motion is to release new version - that should be done

Done via #755