RE: [nant-dev] ANN: New Nant Tasks

[Scott H. <sk...@eo...>]

> -----Original Message-----
> From: Tomas Restrepo
> Hi Scott,
> 
> > I vote for a new NAntContrib Project. This project can take code
> > donations, will allow cvs access for anyone who has tasks they want
to
> > add, and will allow some interesting experimentation without
affecting
> > the core stability, release schedules, or development of NAnt.
> >
> That sounds good to me. In many ways that's what my BuildTasks lib
does:
> provide my own playground for NAnt extensions. If such a project where
to
> surface, I'd be happy to contribute my code to it.

Cool. I'll submit a request for a new project from SourceForge. If
anyone else is interested, please send me email and I'll get back to as
soon the project exists.

> > What modification have you made to NAnt? (You mentioned fixes before
in
> > another email.)
> 
> The largest one is one I mentioned here quite a while ago, which
allows
> project's properties to flow through nant invocations when the nant
task
> is
> used inside a project.
> I have since done a few changes to it, but it's still essentially the
> same.
> However, since some changes where introduced to nant in the specific
files
> I
> modified, I have to keep them synchronized and reapply my patches when
a
> new
> version of Nant comes along...

Understood. I think this support should be in NAnt. Ant has this
support. It has an inheritAll attribute and support for Property child
Elements for <ant/>. The default for inheritAll is true; it is not
required.

Would this format work for you?