Troy Laurin wrote:
On 9/20/05, Gary Feldman <[EMAIL PROTECTED]> wrote:
but on the other hand there are some
things that make can do easily, but which are tricky or more work to do
in NAnt - such as adding a project-wide pre or post compile step.
That actually sounds like a good idea... do you think there would be
demand for an AOP-style framework for NAnt, so tasks can be extended
by registering pre- and post-task event listeners which can inspect
the task's parameters and optionally modify those parameters, or
trigger some other action?
I don't think that AOP has crossed the chasm yet, and the way it
violates the principle of locality of reference makes me wonder whether
it's appropriate for the typical NAnt user. Another idea might be to
just have a mechanism to set defaults. For example,
value="OURSYMBOL=1;BUILDTYPE='nightly'" />
This also violates locality of reference, but in a way that I think
attracts more attention and is easier to remember.
Gary
I can't think of a useful example off the top of my head,
unfortunately. Would anyone else find this useful in some way?
---
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers
