Hello Gary,
It could be a new problem, not an old one. It was reported once, and it
probably occurs in certain very seldom and specific cases.
It will help a lot if I could reproduce this problem on my computer - in
that case it will be more or less easy to fix it.
Please answer the following questions, if possible (you could reply to
support@tmatesoft.com directly):
1. do you have something special in files you're going to commit?
2. could you send me your working copy exactly as it was before commit?
3. what version of Subversion server do you use?
4. what protocol do you use to access repository (svn, http, svn+ssh, file)?
5. do you access repository through the proxy?
Thanks!
Alexander Kitaev.
_____
From: Gary McWilliams [mailto:gary_mcwilliams@lagan.com]
Sent: Monday, July 24, 2006 5:31 PM
To: users@subclipse.tigris.org
Subject: [Subclipse-users] weird problem with JavaSVN and subclipse 1.1.x
I've installed eclipse 3.2 and am using it to work with an existing
workspace (that was created with eclipse 3.1.2 & subclipse 1.0.x) - i.e. I
startup eclipse 3.2 and opened the existing workspace.
If I have JavaSVN selected as the default interface, I get an error on
commit (if I change to javahl, it works correctly):
svn: Unexpected end of svndiff input
I understand (think?) that this was an old known-issue that has been fixed.
I have checked the JavaSVN.jar file in the subclipse plugin and it is
1.1.0_beta2, which should be fine.
Has anyone else encountered this?
Should I create a new workspace when moving from subclipse 1.0 to subclipse
1.1? (is it affected by moving from eclipse 3.1 to 3.2)?
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 Mon Jul 24 15:39:22 2006