On Wed, Nov 19, 2014 at 7:11 AM, Philip Martin <philip.martin_at_wandisco.com>
> "Fitzpatrick, Ben" <ben.fitzpatrick_at_metoffice.gov.uk> writes:
> > This bug prevents use of GNOME keyring password caching by Subclipse:
> > http://subversion.tigris.org/issues/show_bug.cgi?id=3498
> > There's been no news since 2012, and the issue is marked against the
> > 1.7.0 milestone. Is it likely that there will be any progress on this?
> I'm not familiar with eclipse and the issue doesn't identify the cause
> of the problem. Does the problem still occur? Which versions of
> Subversion are affected? What API is Subclipse using?
> I wrote some Java clients to allow me to play with JavaHL authn, see
> r1640533. Using these clients the keyring works when using the new
> org.apache API in 1.9. It also works using the old org.apache API in
> 1.9, 1.8 and 1.7. It also works using the very old org.tigris API in
> 1.9. However I can't get the keyring to work with very old org.tigris
> API in 1.8 or 1.7. In 1.6 only the very old org.tigris API is available
> and enabling the keyring appears to prevent authn working at all. I'm
> seeing a failure to prompt, or to save, but not the hang reported in
> 3498. I suppose this might be the same problem but it's hard to tell
> because the problem has not been fully diagnosed in the issue.
> It's possible that upgrading Subversion, or the APIs used by Subclipse,
> might fix the problem.
Subclipse uses the org.apache API. This issue is definitely related to the
nuances of the code running in Eclipse. Eclipse is an OSGI environment so
there are many layers of Java class loaders involved in loading and running
the code. Eclipse also uses its SWT framework for the GUI. This wrappers
GTK on Linux and I am sure that is a factor here as well.
Unless the error details which have been previously shared give you some
hints, then testing this problem in all likelihood would require running
the test code from an Eclipse plugin context.
Received on 2014-11-19 14:52:40 CET