Actually, I was thinking if people liked this, it could be changed to
<compilewithwalls  file="descriptor.xml"> (or whatever name you like, I don't mind if it's changed)

instead of embedding the descriptor in the xml file.  I didn't know if it would be liked or not and was just testing the waters.  I will make that change also.  For the cc task then it would look like so????....


Is this what you meant Matthew?

Inger, Matthew wrote:
RE: [Ant-contrib-developers] new ant task

I'll clarify my comment about the <cc> task.  It sounds
like you're making an XML descriptor to automate the build
process for a java project.  The same thing would be nice
for the cc task.  Basically, to keep developers out of the
ANT script, and let them be able to add libraries,flags,
etc... to the build process.

Matthew Inger []
Software Developer
Synygy, Inc
610-664-7433 x 7770
"Man who jump off cliff, leap to conclusions." - Confucious

-----Original Message-----
From: Dominique Devienne []
Sent: Thursday, September 04, 2003 11:49 AM
To: 'Stefan Bodewig';
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 []
> Sent: Thursday, September 04, 2003 10:11 AM
> To:
> 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?
> Stefan

This email is sponsored by:ThinkGeek
Welcome to geek heaven.
Ant-contrib-developers mailing list