DITA Open Toolkit

Logged In: YES
user_id=174984

Thank you for the good ideas! Another approach could
involve creating a temporary input ditamap file that bears
the desired file name prior to tasking the toolkit;
however, I was hoping to eliminate the need for such
pre/post DITA ops. I can certainly work with what's
currently available.

Logged In: YES
user_id=1552856

For CHM generation, you can modify
the 'build_dita2htmlhelp.xml' as following:
target: compile.HTML.Help
Add
<move file="${dita.map.output.dir}${file.separator}
${dita.map.filename.root}.hhp"
tofile="${dita.map.output.dir}${file.separator}
${output.name}.chm"/>
at the end of the target.

For PDF, modify the build_dita2pdf.xml.
Target: topic2pdf, map2pdf
Replace the output param with
${dita.map.output.dir}${file.separator}${output.name}.pdf

And you can specify the output name using output.name in
the ant parameters.

Logged In: YES
user_id=174984

Using <move> would require my tooling to know exactly what
the name and path of the generated output articat is;
however, I'm sure that can be determined in advanced for
most cases. Despite the work-around, I believe having the
option to specify the artifact's primary output name will
prove useful.

Logged In: YES
user_id=1151532

I think that by simply use the <move> in ANT can help you
get the output file renamed.