Could you tell me if you found a less ridiculous (cryptic) way to factorise your tasks into a common include file
other than the wonderfully "only it's mother could love it" syntax such as :

<?xml version="1.0"?>

<!DOCTYPE DOCUMENT [<!ENTITY include SYSTEM "file:../common.xml">]>

<project name="toto" default="usage" basedir="." >

&include;

.....


WH

Hello Adam,
I just can explain how we have structured our build process.
We have basically the Project Root Directory beneath which all our projects
are stored. In this directory, we have central includes, which can be
included by all our build scripts. On top of this there is a global.properties file,
where e.g. Directories for our JBoss Installation and the Webserver are
stored in properties. In each project we have a build.xml file, which includes the common targets
and properties, and also defines some project specific targets and properties
(e.g. the classpath). Also we are using a project.properties here, where for
example the name of the project is defined. These properties should never be
overwritten.
Last but not least we have a build.properties stored in the userhome
directory, where each developer can store properties specific for him (e.g.
debug=on, ...). The property files get read in the following order:
- userhome\build.properties
- projectroot\project\project.properties
- projectroot\global.properties

This is how we made a very easy way on how to use ant. I am currently
waiting to get 1.5.2 because there you can include targets from another file and
overwrite them in the build.xml specific to your project.

Greets

Markus M. May



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to