If you really wanted you could "break" up one big build.xml into a set of smaller .xml files and use the <import> task to bring them all back together at run-time...
"Frank W. Zammetti" <[EMAIL PROTECTED]> wrote: Not really... each target performs a specific task, and the one main target antcalls all the others in the proper sequence. It's really no more complicated than a series of method calls. Each target, or method in the analogy, is fairly small and simple, there just happens to be a fair number of them. As with writing actual code, if you space things well and comment decently, the visual cues of where the various parts are makes it look relatively organized. Frank THUFIR HAWAT wrote: > On 7/31/05, Frank W. Zammetti wrote: > >>50 lines? >> >>I have one script that is upwards of 700 lines. I wouldn't worry about >>50 ;) >> >>Frank > > > > How do you organize that? 700 lines is just way too big to read, isn't it? > > -Thufir > > > > -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
