[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

[Subclipse-users] svnant no longer working

From: Gary McWilliams <gary_mcwilliams_at_lagan.com>
Date: 2006-10-27 14:52:56 CEST

I have upgraded subclipse to 1.1.8 & tortoise to 1.4, so my local svn
files are at svn 1.4 level.
 
When I run an ant build it complains about files not being under version
control.
So, I figured, I should get the latest svnant and use that. So I have
checked it out and built it and now the svn tasks are running (i.e. no
longer complaining about files not being under version control), but
*my* getLatestRevision task (below) just no longer works.
 
The task is defined as:
<target name="getLatestRevisionNumber" depends="svn.init">
<echo message="svn.javahl:${svn.javahl}" />
<echo message="svn.username:${svn.username}" />
<echo message="svn.password:${svn.password}" />
<svn javahl="${svn.javahl}" username="${svn.username}"
password="${svn.password}">
<status path="${co.dir}"
lastChangedRevisionProperty="svn.lastCommitRevision"/>
</svn>
<property name="svn.tag"
value="${buildDate}_${svn.lastCommitRevision}"/>
</target>

 
I have added the echo messages for debugging.
 
When I was using subclipse 1.1.6 and an old version of svnant, this
worked a treat:
getLatestRevisionNumber:
[echo] svn.javahl:false
[echo] svn.username:${svn.username}
[echo] svn.password:${svn.password}
[svn] Using javasvn
Svn : Status
[echo] svn.rev:1418

When I run the same target using the latest (svnant/trunk) code, I
always get back an empty string, never the revision number.

getLatestRevisionNumber:
     [echo] svn.javahl:true
     [echo] svn.username:xxx
     [echo] svn.password:xxx
      [svn] Using javasvn
      [svn] <Status> started ...
      [svn] <Status> finished.
     [echo] svn.rev:

I have tried setting svn.javahl=true which makes no difference. I also
tried feeding in a valid user/password which also made no difference.

Is svnant (status) compatible with 1.4?

Am I doing something wrong?

 

The information in this message is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this
message by anyone else is unauthorized. If you are not the intended
recipient, any disclosure, copying, or distribution of the message, or any
action or omission taken by you in reliance on it, is prohibited and may
be unlawful. Please immediately contact the sender if you have received
this message in error.

Received on Fri Oct 27 14:52:21 2006

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.