BTW, when generating the HTML page, the DVSL script inserts a "2000-2003" at
the end.
But there could also be "2000-2004" or more complicated "2000-2002,2004" ...
And it 
could be different for different files.
The value could be specified in the mergefile and the source file.

Ok, not very important at the moment, but we have to have an eye on that (I
think)...


Jan

> -----Ursprüngliche Nachricht-----
> Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Gesendet am: Dienstag, 7. September 2004 08:00
> An: [EMAIL PROTECTED]
> Betreff: cvs commit:
> ant/proposal/xdocs/src/org/apache/tools/ant/taskdefs SubAnt.xml
> 
> jhm         2004/09/06 22:59:37
> 
>   Modified:    
> proposal/xdocs/src/org/apache/tools/ant/taskdefs SubAnt.xml
>   Log:
>   Integrate <subant> complex example into mergefile.
>   
>   Revision  Changes    Path
>   1.10      +58 -0     
> ant/proposal/xdocs/src/org/apache/tools/ant/taskdefs/SubAnt.xml
>   
>   Index: SubAnt.xml
>   ===================================================================
>   RCS file: 
> /home/cvs/ant/proposal/xdocs/src/org/apache/tools/ant/taskdefs
> /SubAnt.xml,v
>   retrieving revision 1.9
>   retrieving revision 1.10
>   diff -u -r1.9 -r1.10
>   --- SubAnt.xml      9 Feb 2004 21:29:18 -0000       1.9
>   +++ SubAnt.xml      7 Sep 2004 05:59:37 -0000       1.10
>   @@ -67,5 +67,63 @@
>                this snippet will execute the compile target 
> of /opt/project/build1.xml,
>                setting the basedir to projects1, projects2, projects3
>            </p>
>   +        <p>Now a little more complex - but useful - 
> scenario. Assume that we have
>   +        a directory structure like this:</p>
>   +        <pre>
>   +        root
>   +          |  common.xml
>   +          |  build.xml
>   +          |
>   +          +-- modules
>   +                +-- modA
>   +                |     +-- src
>   +                +-- modB
>   +                      +-- src
>   +
>   +        <u><b>common.xml:</b></u><br/>
>   +        &lt;project&gt;
>   +            &lt;property name="src.dir"      value="src"/&gt;
>   +            &lt;property name="build.dir"    value="build"/&gt;
>   +            &lt;property name="classes.dir"  
> value="${build.dir}/classes"/&gt;
>   +
>   +            &lt;target name="compile"&gt;
>   +                &lt;mkdir dir="${classes.dir}"/&gt;
>   +                &lt;javac srcdir="${src.dir}" 
> destdir="${classes.dir}"/&gt;
>   +            &lt;/target&gt;
>   +
>   +            &lt;!-- more targets --&gt;
>   +        &lt;/project&gt;
>   +
>   +        <u><b>build.xml:</b></u><br/>
>   +        &lt;project&gt;
>   +
>   +            &lt;macrodef name="iterate"&gt;
>   +                &lt;attribute name="target"/&gt;
>   +                &lt;sequential&gt;
>   +                    &lt;subant target="@{target}"&gt;
>   +                        &lt;fileset dir="modules" 
> includes="*/build.xml"/&gt;
>   +                    &lt;/subant&gt;
>   +                &lt;/sequential&gt;
>   +            &lt;/macrodef&gt;
>   +
>   +
>   +            &lt;target name="compile"&gt;
>   +                &lt;iterate target="compile"/&gt;
>   +            &lt;/target&gt;
>   +
>   +            &lt;!-- more targets --&gt;
>   +        &lt;/project&gt;
>   +
>   +        <u><b>modules/modA/build.xml:</b></u><br/>
>   +        &lt;project name="modA"&gt;
>   +            &lt;import file="../../common.xml"/&gt;
>   +        &lt;/project&gt;
>   +        </pre>
>   +
>   +        <p>This results in very small buildfiles in the 
> modules, maintainable
>   +        buildfile (common.xml) and a clear project 
> structure. Additionally
>   +        the root buildfile is capable to run the whole 
> build over all
>   +        modules.
>   +        </p>
>        </section>
>    </external>
>   
>   
>   
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

Reply via email to