any progress on this one?
i think the big refactoring that just happened was in support of 0.9.0, but
what ever happened to 0.8.0?
also, are the items on the TODO page current? are those what's needed to
get to the different milestones? i would love to see nant get to 1.0 so
more people would
> -Original Message-
> From: Jorge Bermejo [mailto:[EMAIL PROTECTED]]
> Sent: Friday, September 06, 2002 6:12 PM
> To: 'Shaw, Gerry'; '[EMAIL PROTECTED]'
> Subject: RE: [nant-dev] Modified LoopTask...
>
>
> Gerry-
> That's precisely the point, I "Do" want users to override (or
> trash)
Gerry-
That's precisely the point, I "Do" want users to override (or trash) default
property values whenever they need to, In our specific case Nant needs to
prepare/configure the testing environment for Web services/Website
unit-testing and since each user might have different website names, port
I definitely think that defining what a legal property name is would be a big benefit.
As it stands, "" is a legal property name, I can write and it's legal. This has a practical
consequence, in that I think it's currently impossible to correctly parse the -D
argument if you don't know what th
This is an interesting patch but with its current implementation I think
it's a bit dangerous. The potential for trashing pre-set properties is
quite high. The intention of the property attribute on the loop task was so
that you as the build author know what property is going to change. With
th
Hello all,
I've modified the LoopTask to iterate over XML elements defined in an
external file, this new behavior will create multiple Project.properties out
of its attributes.
This can be handy when end-users (release managers) need to modify the build
behavior without touching the build files
