Subclipse is written to JavaHL. Support for SVNKit is possible based
on its implementation of the JavaHL interface using their low-level
library. In Subclipse, it is all the same code and just the JavaHL
interface implementation is swapped out to use SVNKit vs. the native
SVN libraries. The fact that Subclipse works with JavaHL shows this
is an SVNKit problem.
The jsvn scripts that SVNKit provides are just another implementation
they wrote that use their low-level libraries. The fact that it works
properly only means they implemented their library correctly in that
implementation. Apparently they have a bug in their JavaHL
implementation where they are not sending the right notifications.
The messages we show in the console are just echoing the notifications
we receive from the library. Evidently SVNKit is sending
notifications not sent from JavaHL.
On Mon, Dec 13, 2010 at 7:53 PM, Seb Baz <sebbaz_at_gmail.com> wrote:
> I'm having the same problem with svnkit-1.3.4.6888.
>
> As it happens, the SVN repo I'm using is currently locked using a
> commit-hook, but that's not particularly relevant.
>
> In Eclipse+SVNKit, I just get the message "Skipped" in the Console;
> there is no indication of an error anywhere.
>
> Switch to Eclipse+JavaHL and I get a message such as:
>
> svn: Commit failed (details follow):
> svn: Commit blocked by start-commit hook (exit code 1) with output:
> Write access is currently disabled.
>
> There is also a popup dialog box with the same information, so it's
> really obvious the the commit has failed.
>
> Now when I use the jsvn command-line version of the same version of
> SVNkit, I get the message:
>
> Skipped 'null'
> svn: Commit failed (details follow):
> svn: Commit blocked by start-commit hook (exit code 1) with output:
> Write access is currently disabled.
>
> This suggests that the problem may be in Subclipse rather than SVNkit,
> as clearly SVNkit can return the error details to the caller.
>
> On 6 July 2010 15:18, Mark Phippard <markphip_at_gmail.com> wrote:
>> Can you send a mail to support_at_svnkit.com and not the version of the
>> SVNKit library you have installed? I think the latest is 1.3.3.
>>
>>
>>
>> On Tue, Jul 6, 2010 at 10:14 AM, Rob Gansevles <rgansevles_at_gmail.com> wrote:
>>> I am using SVNKit on Linux.
>>>
>>> svn, version 1.6.12 (r955767)
>>> compiled Jun 21 2010, 22:39:25
>>>
>>> A co-worker on windows7 got the same 'Skipped' message when using SVNKit.
>>> When he used JavaHL he got the out-of-date error.
>>>
>>> Rob
>>>
>>> ------------------------------------------------------
>>> http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2630077
>>>
>>> To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
>>>
>>
>>
>>
>> --
>> Thanks
>>
>> Mark Phippard
>> http://markphip.blogspot.com/
>>
>> ------------------------------------------------------
>> http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2630080
>>
>> To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
>>
>
> ------------------------------------------------------
> http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2690544
>
> To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
>
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2690559
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2010-12-14 03:46:04 CET