cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <>
Subject RE: One XML file for build.xml?
Date Fri, 18 Jul 2003 14:03:49 GMT
Berin Loritsch wrote:
> Carsten Ziegeler wrote:
> > Hi,
> > 
> > some months ago the build.xml was split into different files.
> > Although this should create more maintainability and overview,
> > it's actually imho worse. You have to open different files
> > at the same time, as for example properties are declared in
> > the init.xml and you want to edit a different one. The files
> > are not valid xml files and finally you can't use all these
> > great ant build file editors (e.g. the one integrated in eclipse).
> IMO, properties should be declared in a properties file unless you
> are using that XMLProperties ANT task.
Most of them are.

> As to including functionality and calling ANT tasks in other
> XML documents--do not use element includes.  ANT has an <import>
> statement and an <ant call/> setup that can work with targets
> declared in another ant build file.
> The end result is that you can keep modularity without breaking
> all the wonderful build file editors.
Currently, they are included by xml entities :(
If there is an import in ant, this could solve the problem as well,
yes. Didn't know that it exists.

So, this seems to be a valid alternative.

What do others think?


View raw message