IF YOU ARE UNABLE TO VIEW THE GRAPHICS IN THIS EMAIL, PLEASE VISIT HTTP://WWW.BEYONDIGITAL.COM TO ENJOY THE FULL EXPERIENCE.BEYONDIGITAL RESPECTS YOUR PRIVACY. TO UNSUBSCRIBE FROM FUTURE PROMOTIONAL EMAILS BY BEYONDIGITAL, PLEASE VISIT HTTP://WWW.BEYONDIGITAL.COM/OPTOUT.YOUR ADDRESS WILL BE REMOVE
Am I missing something. Is there a task that will let me retrieve
environment settings? I seem to remember talk about extending the property
tag to do this but it got shot down.
If one is not present I would be happy to submit one.
Kevin Miller
-
Sounds like a good addition. What do you plan to do about failures and
errors generated from the . It wont be able to fail the build in
the correct place if you dont wait for it to finish
I think this is why Ant has the parallel task. The parallel task is
synchronous but all the tasks inside c
Andy Sipe wrote:
> I noticed that the exec task always waits for the program to exit
> before moving on. We want to use NAnt as a driver for system level
> regression tests. For this we need to be able to start an application
> and move on to the next target before the application finishes.
I noticed that the exec task always waits for the program to exit before moving on. We want to use NAnt as a driver for system level regression tests. For this we need to be able to start an application and move on to the next target before the application finishes.
Is there any reason that
Hi,
I have been using Nant to make a small example project using code generation
with XSLT. My example worked fine when using tha msxsl.exe from microsoft to
do the actual conversion, but when I use the Nant style task, all '>' get
converted to '>'. This of course makes sense when writing XML do
