[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: JavaHL updates needed/wanted

From: Hyrum K. Wright <hyrum_wright_at_mail.utexas.edu>
Date: Sat, 17 May 2008 23:44:18 -0700

Hyrum K. Wright wrote:
> Mark Phippard wrote:
>> I was reviewing the KWallet branch and noticed that it did not support
>> JavaHL. Looking at SVNClient.cpp, it looks like it would probably be
>> pretty easy to add this support. I was going to try it, but KWallet
>> added a new private function in cmdline.c to check for the library and
>> I was not sure if that code would straight-copy to C++ and work right.
>>
>> While looking into this I noticed something I never realized. The OSX
>> keychain code is also missing from JavaHL. So it would be great if
>> someone could add that. It looked like the Windows crypt code was
>> there.
>>
>> Also, the recent plain-text-passwords branch added some new callbacks
>> and these were not added to JavaHL. It would be nice if a GUI user
>> could receive the same warning as a command line user and have the
>> option to store or not store the passwords.
>>
>> I am willing to test patches for all of the above. I have the
>> necessary OSX and KDE build systems all ready to go to test. I
>> realize these would both be relatively hard for someone not using a
>> tool like Subclipse to test, so I'd be happy to help in this area.
>
> I can take a look at this over the weekend.

It appears I spoke too soon. Instead of working on the kwallet
integration with JavaHL, I instead spent the weekend working on
JavaHL-related stuff for issue #3200, which is a candidate for 1.5, and
which I felt had higher priority. Sorry. :/

I can still look at the JavaHL/kwallet stuff, but it may be a few days
more. If somebody beats me to it, it won't hurt my feelings at all.

-Hyrum

Received on 2008-05-18 08:44:53 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.