> I think it's just a different design.
> In mine the "common" build file already contains everything I
> need for a
> typical project out of the box.
> The purpose of the including build file is just to add/rewrite/extend
> custom stuff. For very basic projects it just adds a target
> to pack the
> build products. For very complex projects it can import several other
> xml files, which in this case can be (and usually are) "incomplete".
I use different types of "common" files.
One common.xml with several common targets. E.g. starting junit, javadoc,
compile etc.
Second family is a set of define-*.xml files where I define several new
tasks using
<*def> family. E.g. for exporting a Rational Rose diagram to HTML a
define-rosewp.xml
or very simply a <print> task for printing one file like
<project name="common-define-print">
<macrodef name="print">
<attribute name="file"/>
<sequential>
<concat taskname="print"><fileset dir="."
includes="@{file}"/></concat>
</sequential>
</macrodef>
</project>
Jan
