env.sh classpath when using ant

[gdelory]

Hi all,

I know the documentation seems to say it: the ant script doesn't load the classpath from the env.sh, but I'm wondering if there is any reason the ant script was never updated to do so. I know the recommended way to run the dita-ot is to use the dita command, but we are working in environment where we don't control how the dita-o is started, and it does still use the ant script.

I didn't really want to set the classpath manually, so instead I've added those 2 lines to bin/ant:

export DITA_HOME=$ANT_HOME
. ${DITA_HOME}/config/env.sh

but I'm wondering why this is not done in the official release, the same way it's done in the dita script. That prevents any plugin bringing their own jars using the dita.conductor.lib.import extension point to work properly with the ant script, unless the classpath is manually edited to add those jars.

Did I miss something obvious when using ant instead of dita, or any thoughts on this? Thanks!