$ echo $UID # return my user ID
I want to use this information within an ant-buildfile. A solution is to set this variable explicitly:
ant some-target -DOWNER_UID=$UID
This way, in my buildfile "${OWNER_ID}" is available for usage.
Is there a way to get this information within the buildfile in an "internal" way, without the need to pass the $UID as parameter?
Not a cross-platform solution, but the following is likely to work in most Unix-like environments:
<exec executable="id" failonerror="true" outputproperty="uid">
<arg value="--user"/>
</exec>
<echo>uid: ${uid}</echo>
If you are talking about accessing an environment variable ($UID) in Ant, you can do like this:
<property environment="env"/>
<echo>UID: ${env.UID}</echo>
See the documentation for the Property task.
My nant script to execute sqlplus.exe looks like following
exec program="sqlplus.bat"
basedir="${base.dir}"
workingdir="${base.dir}" output="log.txt" failonerror="false" resultproperty="execresult"
arg line="${app.sqlplus} ${db.username} ${db.password} ${db.schema} ${var.exec.file} ${db.username} ${db.password}"
end exec
SqlPlus.bat has following contents
echo exit | %1 %2/%3#%4 #%5 %6 %7
I would ideally want to check the "execresult" which is the error code from exec command and show the respective message.
I have tried using the following statement in my SQL file but it did not help.
WHENEVER SQLERROR EXIT SQL.SQLCODE
Could you please point out the problem and possible solution ?
Easiest answer is to remove the output and failonerror on your exec task because then NAnt will naturally show the message as it fails the build. I'm guessing you've avoided that because you want to handle some non-zero exit codes as warnings or success because you want to handle some non-zero exit codes as warnings or success. In that case:
<loadfile file="log.txt" property="execoutput" />
<fail if="${int::parse(execresult)>8" message="${execoutput}" />
I'm working on a project to develop a custom Ant task.
As part of automated acceptance testing, I'd like to execute Ant from JUnit (the opposite of the usual desire) and pass it a string containing certain build XML to be tested via a command line param or stdin or pipe or something like that, rather than referring it to a buildfile on disk.
Is there any feasible way to do this?
Ant expects a file as input. You can however use the -f parameter to specify a tempfile as input:
$ cat <<EOF > tmp1.xml
<project name="demo" default="hello">
<target name="hello">
<echo>hello world</echo>
</target>
</project>
EOF
$ ant -f tmp1.xml
Obviously from Junit you're more likely the write the XML from Java :-)
I am executing ant script in windows. In that consider that, i am executing dir command in exec task as below
<target name="dummy">
<exec executable="cmd" failonerror="true">
<arg line="/C DIRR"/>
</exec>
<exec executable="cmd" failonerror="true">
<arg line="/C cd /d c:\temp"/>
</exec>
</target>
Here I have given DIRR instead of DIR, this execution will fail. but the ant build is not failing. Its showing the error message as dirr is not recognised as internal or external command and the next command cd /d c:\temp also got executed. I want the ant script execution has to be stopped once error message comes.
I want to this script has to stop executing if error occurs in any one of the exec command. failonerror is also not helping. How to fail the ant build, if exec fails.
Note : I am using ant 1.8.2
Please note, that there are two levels of execution here:
Ant calls cmd.exe.
cmd.exe executes DIRSS.
You see, if the the second step fails, this does not necessarily mean, that cmd.exe does propagate the error back to Ant. This might be more obvious if the mentally replace the well-known cmd.exe with something "innocent" like foo.exe.
So the next step is to explore, why the second step behaves differently on your machine than on the machines of the commentators of your question. After that riddle is solved, you can get back to the Ant question.
A first step might be this: Open a new shell window and try
> cmd /c dir
> echo %ERRORLEVEL%
> cmd /c dir nonexisting-directory
> echo %ERRORLEVEL%
> cmd /c dirr
> echo %ERRORLEVEL%
Also tell us the version of your OS.
The Ant exec task has an output property which can be used to tell Ant where the output goes. I've used it to redirect the output to a file. The thing is, if I don't do something with the output, the stuff that Ant prints isn't that much of a help - it's not complete.
Is there someway of setting the output property to System.out?
When executing a batch file with ant's apply or exec tasks on Windows, I found there are special cases where some of the stdout and stderr is not captured by ant. (For example: if you call a batch file that in turn calls other commands (like node.exe), then the stdout and stderror from the child node.exe process is lost.)
I spent a long time trying to debug this! It seems that the batch file's stdout and stderr is captured, however commands called by the batch file are somehow not seen by ant. (perhaps because they are separate child processes). Using the output and error attributes as suggested above doesn't help because only some of the stdout and/or stderr is captured.
The solution I came up with (a hack) is to add these arguments at the end of the command:
<!--Next arg: forces node's stderror and stdout to a temporary file-->
<arg line=" > _tempfile.out 2<&1"/>
<!--Next arg: If command exits with an error, then output the temporary file to stdout, -->
<!--delete the temporary file and finally exit with error level 1 so that -->
<!--the apply task can catch the error if #failonerror="true" -->
<arg line=" || (type _tempfile.out & del _tempfile.out & exit /b 1)"/>
<!--Next arg: Otherwise, just type the temporary file and delete it-->
<arg line=" & type _tempfile.out & del _tempfile.out &"/>
Because this hack only applies to windows, remember to add #osfamily="windows" to the apply or exec task. And create similar task(s) for `#osfamily="unix", etc but without these extra arguments.
The output of exec does go to standard out unless you specify the output attribute.
If you want to output to System.out, then simply do not specify the "output" attribute. If you would like to redirect to a file AND print it to System.out, you can use the tee command, which will redirect output to a given file and also echo it to standard out... I do not know if Windows supports "tee" or an equivalent.
Maybe you want to look at the error, logError, and errorproperty attributes of the exec task too. These deal with the handling of the standard error stream from the exec'd process. There may be useful information there that is going awol for some reason - which might account for the incompleteness you see.
But, if the exec'd process decides to close stdout or stderr and send them elsewhere - there's little you can do.
I have faced similar problem: the output of command execution was suppressed. Perhaps that is the side effect when running cmd under WinXP (I an using maven-antrun-plugin). Anyway setting output="con" worked out perfectly:
<configuration>
<target>
<exec executable="cmd" output="con">
<arg value="/c" />
<arg value="..." />
</exec>
</target>
</configuration>
Working with Ant and Gruntjs:
For anyone trying to get this to work using Gruntjs. I was able to get it working by doing the following (in combination with darcyparker's answer).
In my Ant Build File:
<target description="run grunt js tasks" name="grunt">
<exec dir="/path/to/grunt" executable="cmd" failonerror="true">
<arg value="/c"/>
<arg value="jshint.bat"/> // I broke each task into it's own exec
<arg line=" > jshint.log 2<&1"/>
<arg line=" || (type jshint.log & del jshint.log & exit /b 1)"/>
<arg line=" & type jshint.log & del jshint.log &"/>
</exec>
<exec dir="/path/to/grunt" executable="cmd" failonerror="true">
// another grunt task (IE: uglify, cssmin, ect..)
</exec>
</target>
jshint.bat
#echo off
pushd "C:\path\to\grunt\"
#ECHO _____________________________________________
#ECHO GRUNT JSHINT
#ECHO _____________________________________________
grunt jshint --stack >>jshint.log
NOTE: Path to grunt would be where your Gruntfile.js is located. Also note, I had to initially create the log file (to get it to work with darcyparker's answer) which would output the stack trace from that particular task. This would then give me the grunt task stack output from wherever I call my ant target.
Finally note that pushd "C:\path\to\grunt\" won't be necissary if your bat files are in the same directory as your Gruntfile.js.
I was experiencing this same kind of issue trying to get the build process to fail in Ant after Karma tests intentionally failed, and executing them with "grunt test".
Just added /c before "grunt test", and it worked like a charm
<target name="unittest">
<echo>*** KARMA UNIT TESTING ***</echo>
<exec dir="api_ui" executable="cmd" osfamily="windows" logError="yes" failonerror="true">
<arg value="/c grunt test"/>
</exec>
</target>