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

Re: svnClientAdapter not building due to javasvn dependency

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2005-01-06 02:08:24 CET

"Andy Cutright" <Andy.Cutright@borland.com> wrote on 01/05/2005 08:02:31
PM:

> hi all,
>
> i've pulled the HEAD from the sublicpse SVN repository (i believe).
> there's a subdirectory
> .../src/main/org/tigris/subversion/svnclientadapter/javasvn. this code
> has dependencies on javasvn, so the client won't build. is this a known
> issue? also, how do i find the source for the 09.2.4 release? i've taken
> a look at
> http://svn.collab.net/repos/subclipse/tags/svnClientAdapter/0.9.4/svnCli
> entAdapter/src/main/org/tigris/subversion/svnclientadapter/
>
> but that appears to be missing a large number of files. the source
> builds but the resulting jar fails to run properly in eclipse. possibly
> i'm not familiar enough with subversion, but my understanding is the
> tags branch typically contains a branch (?) representing some moment in
> time ..

Unfortunately, we do not seem to tag svnClientAdapter when we make
releases. You should just be able to look at the revision number of the
tag and then extrapolate to svnClientAdapter in trunk. The differnces
between 0.9.24 and HEAD should be fairly minimal.

I am not sure why Cedric has not checked in the dependencies for the
JavaSVN work he has been doing, probably an oversight. You should be able
to just download the latest JAR and add it as a dependency. Or you could
even just delete the javasvn package. It isn't currently used anyway.

Mark

_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Thu Jan 6 12:08:24 2005

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

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