Re: [basex-talk] Basex Docker Container: How to Control Options

> Really? Really. We may switch to a different format in future (it hasn't been important enough so far).

Re: [basex-talk] Basex Docker Container: How to Control Options

Are you really saying that the “# Local options” comment is a necessary part of the configuration file? Really? Because I don’t think a comment should ever a required part of any syntax… If the configuration file needs have labeled components use YAML or XML or something. Cheers, e. -- Eliot

Re: [basex-talk] Basex Docker Container: How to Control Options

Hi Eliot, If you start with a new version of BaseX, in which the .basex configuration file is still empty or non-existent, there may be no "Local Options" comment. I hope the revised Wiki makes this more obvious [1]. Best, Christian [1] http://docs.basex.org/wiki/Options On Sun, Apr 2, 2017

Re: [basex-talk] Basex Docker Container: How to Control Options

Yes, the options were at the end. But looking at the code I don’t see how that could have mattered. Perhaps I missed a detail? Cheers, E. -- Eliot Kimber http://contrext.com From: Christian Grün Date: Sunday, April 2, 2017 at 11:38 AM To: Eliot

Re: [basex-talk] Basex Docker Container: How to Control Options

Hi Eliot, Did you try to specify the option in the local section of the .basex file (at the bottom, after all other options)? Best, Christian Am 02.04.2017 10:52 schrieb "Eliot Kimber" : I’ve worked around the configuration file problem by setting the options on the

Re: [basex-talk] Basex Docker Container: How to Control Options

I’ve worked around the configuration file problem by setting the options on the Java command line by setting BASEX_JVM in my Dockerfile: ENV BASEX_JVM="-Dorg.basex.CHOP=false -Dorg.basex.CATFILE=/opt/dita-ot/DITA-OT/catalog-dita.xml -Dorg.basex.DTD=true -Dorg.basex.SKIPCORRUPT=true" That