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

Re: [Subclipse-users] Url@revision syntax not working

From: Mark Phippard <markphip_at_gmail.com>
Date: 2007-04-24 13:51:51 CEST

Try adding a slash to the end of the URL.

Mark

On 4/24/07, Puneet Lakhina <puneet.lakhina@gmail.com> wrote:
> Hi,
> I have the following basic build file.
> <?xml version="1.0" encoding="UTF-8"?>
> <project default="myTarget">
> <taskdef name="svn"
> classname="org.tigris.subversion.svnant.SvnTask
> "></taskdef>
> <target name="myTarget">
> <svn>
> <checkout url="svn://10.0.52.139:3690" destPath="C:/ant_svn_test"/>
> </svn>
> </target>
> </project>
>
> When i try and build this file i get the following result
> --start result--
> Buildfile: build.xml
>
> myTarget:
> [svn] Using command line interface
> Svn : Checking out a working copy from a repository :
> co -r HEAD svn://10.0.52.139@HEAD C:\ant_svn_test --non-interactive
> svn: Unknown hostname 'HEAD'
>
> BUILD FAILED
> C:\Documents and Settings\puneet\My Documents\ant
> experimentation\build.xml:6:
> Can't checkout
>
> Total time: 13 seconds
> --end result----
>
> I tried executing the same command directly from the command line instead of
> through the svnant task and i still get the same error. But when i try
> something like the following(without the @HEAD syntax)
>
> svn co -r HEAD svn://10.0.52.139 from the command line it works properly.
>
> I believe the problem is the url@revision syntax which somehow my shell is
> not able to recognize. I am using Windows XP.
>
> I would appreciate any help on the issue.
>
> Thanks
> --
> Puneet

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Tue Apr 24 13:52:07 2007

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.