. It looks like you are not expanding,
supporting expressions, for those values unless an additional attribute
dynamic is set. What is the value in this?
It would seem cleaner to me to just let the on attribute be auto-expanded.
- Original Message -
From: James C. Papp [EMAIL PROTECTED
, for those values unless an additional attribute
dynamic is set. What is the value in this?
It would seem cleaner to me to just let the on attribute be auto-expanded.
- Original Message -
From: James C. Papp [EMAIL PROTECTED]
DependsTask Patch
Here is an implementation
Yea, I was thinking the same thing (Ant does it this way), but sometimes you
want the combined output (particularly with Windows command-line tools which
seem not to get the whole stderr, stdout concept), and if you have two separate
properties there is no way to recombined them in the order that
Here is a patch that adds two badly needed features (well..., at least for me
:-)) to the exec/ task.
One is resultproperty, which is used to specify a property that will receive the
exit code of the process (it more useful when failonerror is false).
The other one is outputproperty, which is
Just in case the attachments for the two patches I just submitted did not make
it to the list, they are also available from the sourceforge Patches feature
accessible from the main page.
http://sourceforge.net/tracker/?group_id=31650atid=402870
James.
Well, reintroducing the force attribute seems like a bad idea since it has
already been deprecated (but thanks for asking); its resurrection would
probably just cause too much confusion.
Your solution:
call target=foo unless=target::has-executed('foo')/
(BTW, all the new expression evaluation
(should be available in the next
nightly build), but I fixed this for the csc compiler before ...
What version of NAnt are you using ?
Gert
- Original Message -
From: James C. Papp [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, November 17, 2003 11:57 PM
Subject: [nant
It seems that this a general problem with anything that creates a response
file. I'm seeing the same error the CSC compiler as well.
James.
Quoting James C. Papp [EMAIL PROTECTED]:
BUG: Visual-Cpp tasks fail when path for response file contains a space.
The code currently looks something
Great! I will need to refresh the source with the latest code under CVS (I'm
currently using code released under v0.83), though I do not think that there
will be many changes. Do you want me to zip up the source files that have
changed and post them to the list, or do you want me to use some
RE: [Fwd: Ready to tackle next release]
If you are getting ready for a new release, I have a bunch of patches I would
love to see added to NAnt. I would be willing to work with everyone as much
as needed, to see that the changes make it into the release; or some variation
of them - that is,
options are always written first, they can never override parameters
that NAnt uses
Anyway, this change would simplify our NAnt scripts significantly (we actually
uses a special version of NAnt with this change that we created). So what
does everyone think?
James C. Papp
[EMAIL PROTECTED
significantly (we actually
uses a special version of NAnt with this change that we created). So what
does everyone think?
James C. Papp
[EMAIL PROTECTED]
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http
12 matches
Mail list logo
