Firstly, initialisation, for completeness. In this example it serves no purpose and may be omitted.
Example 9. Initialisation, a preparatory task
<!-- --> <!--Initial processing: If needed. --> <!-- --> <target name="init"> <echo message="Do initialisational things" /> <tstamp><format property="TODAY_UK" pattern="d-MMM-yyyy" locale="en"/> </tstamp> <echo>building on ${TODAY_UK}</echo>
</target>
| This code produces a formatted time value |
| The echo command prints output to the terminal |
To get this out of the way. Sometimes it is useful to carry out some housekeeping prior to running a task. Typically this might be removing all the files in the html directory (if you want to ensure that only new files are created). This is the place to do it. All this example does is to echo the time at which the operation started.
Now the actual phase 1 build i shown in Example 10.
Example 10. Layout processing
<!-- ================================================ -->
<!-- Use layout to create autolayout.xml -->
<!-- Needs to be run if files are added to the Website -->
<!-- ================================================ -->
<target name="layout" depends="init">
<echo message="Website, first stage processing " />
<java classname="${xslt.processor.class}"
fork="yes"
dir="${in.dir}"
failonerror="true">
<classpath refid="xslt.processor.classpath" />
<arg line="-o ${autolayout.outfile}"/> 
<arg line="-x org.apache.xml.resolver.tools.ResolvingXMLReader"/> 
<arg line="-y org.apache.xml.resolver.tools.ResolvingXMLReader"/>
<arg line="-r org.apache.xml.resolver.tools.CatalogResolver"/> 
<arg line="${in.dir}/${autolayout.infile} ${autolayout.stylesheet} ${param.args.post}" /> 
</java>
</target>
| This parameter specifies the xslt engine to use, previously set to saxon |
| What to do in case of an xslt transformation error. Stop! |
| The output file from this transformation, |
| This tells the parser to resolve any references using the Apache resolver (to be explained later...) |
| This brings the catalog resolver into play. Again, more later... |
| These are the input file ($autolayout.infile =
|
That's the full transformation. Of note is the error processing. It is advisable to have the system stop processing on finding an error. Otherwise you could be uploading nothing, or old files to your Website. If the system stops, the errors will be reported to you on the terminal. That way you can resolve them and re-process the Website.
Try corrupting one of the xml files (remove a closing > from one of the elements and find out what happens! You should find it easy to locate and correct the error.
In order to use this command, assuming the ant script/batch file
is accessible from the command prompt, simply change directory to
where the build.xml file is located and issue the command
>ant layout
If there are no errors, the output file
autolayout.xml will be created.
Next, phase two build