Co workers of me also have this problem, and it is reported long tima ago already but until now no progress is made.
But the key problem why they encounter this is because they have to use currently svnkit because they are on linux or running a 64bit windows with 64bit java (which happens more and more) because i want to use javahl i installed 64 and 32bit java on my system and run a 32bit eclipse just for subclipse
And no the current way of saying install this command line client then you get 64bit that doesn't really work for me. I tried and one start of eclipse it did find it, a restart later and i was suddenly using svnkit again. Besides this if i do install a 3th party command line client i have to remember to keep also that up to date. Currently in 32bit i get new native javahl stuff pushed to me.
Also the argument of then just use a 32bit eclipse is not valid, yes i can do that and i am sticking on it. But others dont really know that. They get a system where java is preinstalled on they get an installer of an eclipse based project, they run that and they installer detects that it is a 64bit jvm and installs the 64bit version. After that they also install subclipse and they have no idea that they now use svnkit instead of the native javahl. They even dont know what that is they dont have to be tech persons like us.
So all these people would be really helped if subclipse install would include 32bit and 64bit versions of all major os (win,mac,linux)
----- Original message -----
> 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].
------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2690594
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2010-12-14 08:23:20 CET