ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <bode...@apache.org>
Subject Re: [DISCUSS] EasyAnt: Ant based pre packaged build system for java projects
Date Mon, 14 Jan 2008 13:12:27 GMT
"Dominique Devienne" <ddevienne@gmail.com> writes:

> On Jan 11, 2008 8:11 AM, Stefan Bodewig <bodewig@apache.org> wrote:
>> "Gilles Scokart" <gscokart@gmail.com> writes:
>>
>> > I never thought to overwrite macro to customize a generic build script.  Can
>> > macro be overwritten?
>>
>> Sure, it's just another Ant task that has been defined.
>
> But my point is that most of the time, you never want to override
> things (macros or target), but augment them with some kind of pre or
> post processing.

Hey, I didn't say it was a good thing to do, I just pointed out that
technically you can override a macrodef'ed task just like any other
task.

> Peo's point of simply copy-pasting the "abstract" build code to
> fully override the target duplicates that code, and makes build
> maintenance all the more difficult.

I'm not convinced that we need something like this at the task level,
while I agree we need some better support for it at the target level.

Back during the Ant2 discussions we have been talking about adding AOP
like features to Ant at a well-defined "pointcut"s like target and
task invactions.  This may be overkill, though.

Having something like before/after/around advices (where around is the
same as an override that doesn't change the dependencies list) may
suffice and leave overwriting the whole target definition to the worst
case.

Stefan

-- 
http://stefan.samaflost.de/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message