ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dominique Devienne <>
Subject RE: [Patch] keep-alive feature
Date Tue, 08 Jul 2003 15:16:39 GMT
Are you saying I'm repeating myself ;-) I sure am, am I?

Pluggeable aspects came to me too, I just didn't think throwing it out as
well would have helped much the chances of aspects getting to 1.6...

Short of using real AOP like AspectJ, I don't see how Pluggeable aspects can
be implemented than with some kind of decorator to Task (or Type? Or

Look where ant:type is used... Can you design Pluggeable aspects that would
be able to use that attribute the way it's used now? I think a lot of people
would be perfectly happy with the few aspects mentioned already hard-wired
in Ant 1.6. And leave the generalization to a later date/release. --DD

> -----Original Message-----
> From: Stefan Bodewig []
> Sent: Tuesday, July 08, 2003 10:05 AM
> To:
> Subject: Re: [Patch] keep-alive feature
> On Tue, 8 Jul 2003, Dominique Devienne <> wrote:
> > failonerror, if/unless, ant:type, and some other attributes most
> > likely, control 'aspects' of the build, that should be dealt with in
> > a single place!
> Well, it's not exactly as if we were having that discussion for the
> first time.  Things come back all the time. 8-) The old aspect
> discussion is what fuelled my proposal.
> Yes, I know and I think we are heading for something here.  Another
> aspect (old news as well) would be the logging verbosity - control it
> on a task by task basis.
> I'm not sure I agree with the "single place", though.  Pluggable
> aspect handlers anyone?
> Stefan

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message