[Octave-bug-tracker] [bug #51919] environment variable OCTAVE_JAVA_DIR

[Kai Torben Ohlhus]

Follow-up Comment #2, bug #51919 (project octave):

The conflicting section in the documentation is:

https://hg.savannah.gnu.org/hgweb/octave/file/631076eab47b/doc/interpreter/external.txi#l2112

The description is really misleading: `OCTAVE_JAVA_DIR` must remain a constant
path to `octave.jar`


$ export OCTAVE_JAVA_DIR=/tmp
$ octave-cli

>> javaaddpath("/home") 
error: octave.jar does not exist: /tmp/octave.jar
error: called from
    javaaddpath at line 52 column 13


vs.


$ export OCTAVE_JAVA_DIR=
$ octave-cli
>> javaaddpath("/home") # no error


Therefore I agree, that `OCTAVE_JAVA_DIR` is an example of a useless
environment variable.

I can imagine two solutions:

1. The location of `octave.jar` should not rely on reading the environment
variable `OCTAVE_JAVA_DIR` and is determined at compile/install time.

2. Introduce two environment variables: `OCTAVE_JAVA_DIR` and
`OCTAVE_JVM_OPTS`.  The latter one obtains the JVM parameters directly in
favor of a separate file `java.ops`.

I favor the first solution, as it is not likely that the location of
`octave.jar` will change after the installation.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?51919>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/