Unquoted LOGGING variable in fuseki-server can make server fail to start about jena HOT 6 CLOSED

Good point. I will come up with a solution that can't insert an empty argument.

from jena.

Adding quotes should be ok and fix the issue here. Would you like to send a small pull request for that? Thanks!

from jena.

There is a corner case : suppose "$FUSEKI_HOME/log4j2.properties" does not exist then LOGGING isn't set and $LOGGING expands on the command line to no argument. But if it is quoted, it puts in an empty string argument. And because it has no leading "-" it cuts off the command flags.

Is there a way to put it on the command as a single argument if not the empty string and nothing if empty.

An alternative is to to set LOGGING to some no-op like -Dnosuch=novalue.

from jena.

I've pushed another commit that quotes LOGGING if it's not empty.

The code assumes LOGGING will expand to a single argument. That is,

$ export LOGGING='-Dlog4j.configurationFile=myconfig.properties -DmyLogVar=value'
$ fuseki-server

won't work. I assume this isn't a problem, because the argument could be provided in JVM_ARGS. Let me know if I'm mistaken.

from jena.

No, shouldn't be a problem.

from jena.

I think we're good to go, then. Let me know if there's anything else you need from me.

from jena.