On Fri, 18 Jul 2003, 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. > > 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. I thought we wanted to wait until 1.6 final, and <import> is an official element. > > > > So, I really would like to have one single build.xml again. > > I think we get the same visibility, but have the advantages mentioned > > above. > > > > If noone is against this, I will merge them again. I strongly against. One big build file is a mess, and unmaintainable. I really don't get your point why one big build is the better choice? Stephan.
