Master files with DITA OT Ant builds and properties
Posted: Tue Jul 07, 2020 4:37 pm
When working with Open Toolkit plugins, I'm struggling to find a way to have properties defined in the OT's root build.xml in scope for plugin Ant build files. I'm sure I remember having done this in the past at some point, but I think I'm missing something crucial.
I have a plugin com.example.foo and am working on plugins/com.example.foo/build_foo-example_template.xml. That build includes com.example.bar/build_bar-example.xml, using the OT-defined plugin properties - e.g. so that macrodefs and taskdefs used in bar are available to foo.
If I add the main OT build file (i.e. dita-ot-x.y.z/build.xml - after the OT build and integration) to my Oxygen project master files, I had expected that the include would start resolving and the components in bar would be available while editing, since build.xml is where the *.plugin.dir properties are declared, but that seems not to be the case. What might I be missing here?
I'm using Editor 22.1 build 2020061102 and my working copy is a fork of the main OT trunk (forked from v3.0.3, in case that has any relevance).
Any useful ideas on other/better ways to approach OT plugin development in Oxygen would be gratefully received too, of course
I have a plugin com.example.foo and am working on plugins/com.example.foo/build_foo-example_template.xml. That build includes com.example.bar/build_bar-example.xml, using the OT-defined plugin properties - e.g.
Code: Select all
<include file="${dita.plugin.com.example.bar.dir}/build_bar-example.xml"/>
If I add the main OT build file (i.e. dita-ot-x.y.z/build.xml - after the OT build and integration) to my Oxygen project master files, I had expected that the include would start resolving and the components in bar would be available while editing, since build.xml is where the *.plugin.dir properties are declared, but that seems not to be the case. What might I be missing here?
I'm using Editor 22.1 build 2020061102 and my working copy is a fork of the main OT trunk (forked from v3.0.3, in case that has any relevance).
Any useful ideas on other/better ways to approach OT plugin development in Oxygen would be gratefully received too, of course
