Gary Feldman a écrit :
This looks like a good idea, but could be difficult to do generally
across all tasks.
In the meantime, a simple approach that works today is to duplicate the
task invocation with if/unless attributes, and use a property to
indicate which to do:
In the setup targets:
Just a pie-in-the-sky (whatever that means)...
These kind of issues aren't all that uncommon in builds... how feasible
is a meta-element attribute that can be nested under any
element and decorates it with an attribute. If the
attribute meta-element supported if/unless and lazy property
Troy Laurin wrote:
Just a pie-in-the-sky (whatever that means)...
These kind of issues aren't all that uncommon in builds... how
feasible is a meta-element attribute that can be nested under any
element and decorates it with an attribute. If the attribute
meta-element supported if/unless and
Hi
I usually leave the doc generation always enabled. I just switch
off/on the ndoc call.
Thibaut
2005/4/21, Gary Feldman [EMAIL PROTECTED]:
Troy Laurin wrote:
Just a pie-in-the-sky (whatever that means)...
These kind of issues aren't all that uncommon in builds... how
feasible is a
On 4/21/05, Gary Feldman [EMAIL PROTECTED] wrote:
This looks like a good idea, but could be difficult to do generallyacross all tasks.
I think there is a way to do it, but it is a little more complicated
than I like... Basically the NAnt.Core.Element class could be
extended with late binding
Troy Laurin wrote:
Anyway, I might have a play with it over the next few weeks, and if I
don't find any nasty side-effects with targets or other elements, then
I'll submit it as a patch post-0.85.
PS- no offense, but some of the code to initialise the project and
process the build file could
On 4/22/05, Ian MacLean [EMAIL PROTECTED] wrote:
somthing like this could be a good solution. Another possibility is tohave a way to set an attributes value such that its equivalent to it notbeing set - somthing like null for attributes. For example;target name=notdoc
property name=docFile
