Hello,
> I have to assume that somehow an older version of the JAR is being used.
> Maybe the JavaSVN developers can weigh in with other ideas?
One of the possibilities is that working copy was not properly upgraded
by JavaSVN. Does command line client works on it (run for instance svn
st from the command line)?
If it will happen that working copy is not correctly upgraded and
corrupted try re-checking out it. However, I never experienced such kind
of problem (with incorrect upgrade) with the version of JavaSVN included
in Subclipse 1.1.8.
Also, there is a system property that may prevent JavaSVN from upgrading
working copy - "javasvn.upgradeWC" ("true" by default), but I doubt that
you have it set.
Alexander Kitaev,
TMate Software,
http://tmate.org/
Mark Phippard wrote:
> Kristian Duske <4815162342n@gmail.com> wrote on 11/10/2006 03:31:41 PM:
>
>> at org.tmatesoft.svn.core.javahl.SVNClientImpl.add
>> (SVNClientImpl.java:374)
>> at
>> org.tigris.subversion.svnclientadapter.javahl.AbstractJhlClientAdapter.a
>
>> ddFile(AbstractJhlClientAdapter.java:172)
>> ... 8 more
>>
>> Maybe this will help.
>
> It proves you are using JavaSVN.
>
> I have to assume that somehow an older version of the JAR is being used.
> Maybe the JavaSVN developers can weigh in with other ideas?
>
> Mark
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: users-help@subclipse.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Fri Nov 10 21:46:31 2006