And if you could get that build descriptor type thing
to work with the <cc> task, that would be excellent. :)
Matthew Inger [firstname.lastname@example.org]
610-664-7433 x 7770
"Man who jump off cliff, leap to conclusions." - Confucious
From: Dominique Devienne [mailto:DDevienne@lgc.com]
Sent: Thursday, September 04, 2003 11:49 AM
To: 'Stefan Bodewig'; email@example.com
Subject: RE: [Ant-contrib-developers] new ant task
+1. I don't like the name too much though... Any other suggestions?
Once it's in, it will be easier to make it evolve. The XSL-based system I
currently have, and would very much like to replace with something like this
task, reads the definition of what the project sub-parts are, and which
dependencies they each have, between each other, but also with external
JARs. I enable part of this functionality thru a <buildpath> element that
extends Path, and allows to plug-in a custom BuildPathResolver to determine
the build order. (I've posted that code).
The ability to compile a project's subpart independently is great, but the
exact dependencies between these parts, and for each part of external JARs
is something that I (and I suspect other) really need.
My $0.02. --DD
> -----Original Message-----
> From: Stefan Bodewig [mailto:firstname.lastname@example.org]
> Sent: Thursday, September 04, 2003 10:11 AM
> To: email@example.com
> Subject: Re: [Ant-contrib-developers] new ant task
> I was waiting for anybody else to comment on Dean's compilewithwalls
> task. I really like the idea and would like to see it somewhere.
> Ant is more or less in a no-new-tasks-accepted state and I don't
> expect it to change until after the release of Ant 1.6. Maybe we'll
> see multiple antlibs as subprojects of Ant after that, who knows.
> Dean's task is really useful, well documented and tested IMHO and I
> see it as a good fit for ant-contrib. What do others think?
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
Ant-contrib-developers mailing list