YADE Command Line Client - argument compatibility with YADE branches 1.x

Current Situation

• The YADE Command Line Client (Branches 1.x) supports argument syntax where the argument name and its value can be separated by either an equals sign (=) or a space.
  • The general pattern is: -<argument name>[=]<argument value>
  • Examples:
    • -java-options=... or -java-options ...
    • -log-level=... or -log-level ...
    • -settings=... or -settings ...
    • -return-values=... or -return-values ...
• The YADE Command Line Client (Branches 2.8.x) generally supports 1.x argument syntax (e.g., for -profile and similar arguments).
  • However, some arguments only accept the syntax using equals sign (=), which makes the JS7 YADE client not fully compatible with the 1.x branches.
  • List of such arguments:
    • --java-options=...|-java-options=...
    • --log-level=...|-log-level=...
    • --settings=...|-settings=...
    • --return-values=...|-return-values=...
  • As a result, if the -settings argument is provided using a space as a delimiter, it may not be recognized by the JS7 YADE client.
    • In this case, the JS7 YADE client defaults to:
      • ${JS7_YADE_CONFIG_DIR}/yade.xml, where:
        • ${JS7_YADE_CONFIG_DIR} is an environment variable set by the JS7 agent.
        • It points to the YADE configuration directory corresponding to the agent’s configuration directory, i.e., JS7_AGENT_CONFIG_DIR.

Desired Behavior

• Adjust JS7 YADE CLI start scripts (Unix and Windows) to handle both equals sign (=)  and space delimiters for arguments, ensuring compatibility with 1.x branches.

Workaround

• Use equals sign (=) when specifying arguments that currently do not support spaces.

Patch

• Path for 2.8.x is available. Copy yade.sh into the bin directory of the YADE installation
• https://download.sos-berlin.com/patches/2.8.0-patch/yade.sh  [ sha256 ] [ sig ] [ tsr ]