Hmm
Verbose property is used as well for another purporse. This adds even more
verbosity and is dedicated more to debugging then anything else. Still
verbose could be better if it's made more-level switch rather than
true/false...
Martin
- Original Message -
From: Gert Driesen [EMAIL
Hi all !
1/
Do you think, that now is good time to some
cleaning and restructuring in solution task as we discussed earlier?
I have some spare time and appetite to do that
now!
2/
Also I would need (and like to) make some
improvements to that task. What I need (and currently use
Hi all,
this snippet:
if test=${1==1}
fileset id=f1 basedir=c:\temp\foo
includes name=item3/
/fileset
/if
is currently not possible because type definitions are allowed only at
project or task level. Is it intended or should we allow this as well?
I'm working on extension that
How about a modify-fileset task? Like this:
modify-fileset id=f1 mode=add | delete | replace
fileset
/fileset
/modify
It would take either replace the f1 with the contents of fileset, add
new items or delete matching items.
Jarek
- Original Message -
From: Martin Aliger [EMAIL
Another approach to do the same ;-) If you prefer this, I could do it and
send patch.
Now I already finished mine original idea with multiple filesets. I could
send a patch if you like that approach...
Martin
How about a modify-fileset task? Like this:
modify-fileset id=f1 mode=add | delete
The method Martin proposed has been discussed before. It would be tidier
from a user point of view to allow adding to filesets without a seperate
task - maybe using the mode attribute on the fileset itself
fileset id=f1 basedir=c:\temp\foo mode=append | replace !--
re-define f1 fileset
This is a good thing. We should have enabled this some time ago.
Ian
As a sideefect to enable this I have to enable also use of type-defs in
TaskContainer (used in if and foreach )
---
This SF.net email is sponsored by: IBM Linux Tutorials.
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.
