Not really ;-) GUMP works fine. I'm not trying to replicate it. I'm trying
thru other means though to build a project so that all its dependencies are
correctly fetched (if needed) and used. It's more similar to Maven in that
regard, while retaining the flexibility to use whatever ant build you
need/want (just becomes a utility to simplify/help writing your build).

A GUMP-like build could be achieved with <subant> and what I'm trying to do,
but minus all the reports. Like I said, GUMP works fine, and we're using it
(in a limited fashion), so rewriting it is a waste of time IMHO.

--DD

PS: I'll post the new <subant> with <buildpath> within a few weeks.

-----Original Message-----
From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 14, 2003 10:16 AM
To: Ant Developers List
Cc: [EMAIL PROTECTED]
Subject: Re: subant



Dominique Devienne wrote, On 14/03/2003 17.08:
> This is a completely different issue that I'm addressing independently.
> 
> <subant> is not meant to replace GUMP. Its purpose is to build projects in
a
> given order. It doesn't dictate the classpath used by these projects at
all,
> like GUMP does. Each project is on its own to configure its classpath and
> everything. What it is guaranteed is that its dependencies have been built
> before if is built (provided that project's build is called by a higher
> level build thru <subant>. --DD

Yes, I ACK this, but I'd like to see if I can /use/ subant to have 
Gump-like functionality.

For example, if you added an interceptor system right before each call, 
I can do everything I like before each project call. In this way I can 
subclass subant and make a "gumpant" task, that would be used by centipede.

Does this make sense?

-- 
Nicola Ken Barozzi                   [EMAIL PROTECTED]
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)
---------------------------------------------------------------------


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to