Hi there,
I do have a question concerning the svnAnt status task and do not know where
to post it...
I have an ant script and would like to run the status task on my whole
working directory.
If I would run the following manually on the command line, I would get:
$> svn status
M project.properties
M build.xml
which is what I expect. Now if I run the following target from my build.xml
ant script
<target name="status" depends="init" description="Get the SVN status of a
working copy">
<svn>
<status path="${main.dir}"/>
<svn/>
</target>
It just returns:
Buildfile: build.xml
init:
[echo] Starting on: September 16 2005
status:
[svn] Using javahl
Svn : Status
BUILD SUCCESSFUL
which is obviously not what I was expecting. Apparently the svn status
command line and the <svn><status> task have different behaviors.
If I would like to reproduce the command line behavior in ant, I would need
to loop over every file in my project and call the <svn><status> task on
them which would be taking a lot of time. Therefore I changed my target to
the following and it's working properly (meaning, as I expected :-))
<exec dir="${main.dir}" executable="svn">
<arg line="status"/>
</exec>
Returns:
Buildfile: build.xml
init:
[echo] Starting on: September 16 2005
status:
[exec] M build/project.properties
[exec] M build/build.xml
BUILD SUCCESSFUL
Total time: 1 second
But this is just a work-around which is not completely satisfying.
Finally, my question is:
Would it be sensible and feasible to add an "recursive" additional attribute
to the status task ? Provided that this attribute is true, the <svn><status>
task should display all changes below the "path" provided as mandatory
attribute. This should make the <svn><status> task more similar to what the
svn status command does.
Cheers,
Nicolas Delhomme
Received on Fri Sep 16 21:59:20 2005