Running custom build file
Posted: Fri Oct 01, 2010 12:09 pm
Hi,
I'm trying to run a custom build file with Oxygen, so I have specified the file in the transformation scenario dialog, and I can see in the log that it is being used, so that's no problem.
But the problem is it doesn't seem to care about the properties I set there, which I assumed would override the parameters in the scenario dialog (which won't allow me to leave output.dir empty):
What I want to do is run two consecutive runs, where the windows target is run first (set as depends on default target linux), and then the linux target should run. These have separate output.dir set, so I want the output in different directories.
But again, these output.dir parameters don't seem to come into play. The output ends up in the directory specified in the scenario dialog (c:\ditacontent\out). And strangely, one of them is filtered correctly, the other one has a double extension (perhaps something that happens because there already is a file with the same name after the first run?), but with no content at all, except the xml declaration...
What am I doing wrong?
Regards,
Anders
I'm trying to run a custom build file with Oxygen, so I have specified the file in the transformation scenario dialog, and I can see in the log that it is being used, so that's no problem.
But the problem is it doesn't seem to care about the properties I set there, which I assumed would override the parameters in the scenario dialog (which won't allow me to leave output.dir empty):
Code: Select all
<project name="multiple" default="linux" basedir=".">
<property name="dita.dir" value="${basedir}"/>
<import file="${dita.dir}${file.separator}integrator.xml"/>
<target name="windows" depends="integrate">
<ant antfile="${dita.dir}${file.separator}build.xml" target="init">
<property name="output.dir" value="C:\DitaContent\out\windows"/>
<property name="dita.input.valfile"
value="${dita.dir}${file.separator}demo${file.separator}fo${file.separator}Customization${file.separator}filters${file.separator}windows_filter.xml"/>
<property name="transtype" value="eclipsecontent"/>
</ant>
</target>
<target name="linux" depends="windows, integrate">
<ant antfile="${dita.dir}${file.separator}build.xml" target="init">
<property name="output.dir" value="C:\DitaContent\out\linux"/>
<property name="dita.input.valfile"
value="${dita.dir}${file.separator}demo${file.separator}fo${file.separator}Customization${file.separator}filters${file.separator}linux_filter.xml"/>
<property name="transtype" value="eclipsecontent"/>
</ant>
</target>
</project>
But again, these output.dir parameters don't seem to come into play. The output ends up in the directory specified in the scenario dialog (c:\ditacontent\out). And strangely, one of them is filtered correctly, the other one has a double extension (perhaps something that happens because there already is a file with the same name after the first run?), but with no content at all, except the xml declaration...
What am I doing wrong?
Regards,
Anders