Open Activity Monitor and find Eclipse. Then click the Inspect button
and Open Files and Ports. This shows all the libraries that are open.
Copy and paste it somewhere and search for "libsvn". See if they are
all coming from the same folder.
Mark
On Tue, Jun 18, 2013 at 1:49 PM, Mark Phippard <markphip_at_gmail.com> wrote:
> On Tue, Jun 18, 2013 at 1:39 PM, Jacob Weber <jacob_at_jacobweber.com> wrote:
>>> Did you use SVNKit previously?
>>
>> I'm not certain, but I think I was using JavaHL before I upgraded. I've used SVNKit in the past, though.
>>
>>> Maybe try renaming your .subversion folder temporarily so that it is
>> created fresh.
>>
>> Tried that....same thing.
>>
>> If I remove Eclipse.app from Keychain's "always allow access" list, restart Eclipse, then try to access the SVN repository, it still prompts me for the password, and I don't get Keychain's prompt for whether to allow it access to the keychain. I do get the prompt if I do that with the command-line svn client.
>
> I cannot think of a reason that the JavaHL library would behave
> different from the command line. The JavaHL library is just a thin
> veneer that connects Java to the same libsvn_client that the command
> line uses. Assuming all the binaries came from the same distribution
> I would expect them to behave the same.
>
> I am not aware of any tricks on OSX for seeing which libraries are
> loaded. The OSX crash report includes that information, but unless
> you know a way to force Eclipse to crash I do not know how to get that
> information.
>
> --
> Thanks
>
> Mark Phippard
> http://markphip.blogspot.com/
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=3058421
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2013-06-18 20:00:06 CEST