Hello,
mine 2 cents to this:
- first I liked those pipe idea proposed
- but Gary is mostly right - there is alot stuff possible via output/append
- only missing is input redirection?
exec program=cmd1 output=${filename} /
exec program=cmd2 output=${filename} append=True /
exec
Hmm,
is there any way to share script between Ant and NAnt and still using
proprietary features of both? something like conditionals? Maybe this could
be solution. If not, propably both teams would be needed to code it...
somehing like:
target name=clean
delete dir=${output.dir}
Gert Driesen wrote:
don't support the basedir property.
Ahh pity. From an academic, developer to developer point of view I'm
curious why that decision was made. I'm just wondering because
obviously that's a big decision since many existing Ant scripts use
${basedir} as a property and
NAnt 0.85 (Build 0.85.1932.0;
rc3; 16/04/2005)
Copyright (C) 2001-2005 Gerry
Shaw
http://nant.sourceforge.net
Buildfile:
file:///C:/latch/BizDeploy/BT2004DeployWithNAntSample2.52/src/BizTalkSample.sln.deploy.build
Target framework: Microsoft
.NET Framework 1.1
Target(s) specified:
Hello,
I am receiving the following error while running a Nant build script:
BUILD FAILED
INTERNAL ERROR
System.IO.PathTooLongException: The path is too long after being fully qualified. Make sure path is less than 260 characters.
at System.IO.Path.nGetFullPathHelper(String path, Char[]
On 6/30/05, Martin Aliger [EMAIL PROTECTED] wrote:
Hmm,
is there any way to share script between Ant and NAnt and still using
proprietary features of both? something like conditionals? Maybe this could
be solution. If not, propably both teams would be needed to code it...
Ant and NAnt are
