RE: [Subclipse-dev] Patch for MSCAPI support, when using SVNKIt

> I did notice one problem in the Windows check. It's checking the constant Platform.OS_WIN32, which will never be null or empty, so it will always assume that the platform is windows. I would fix this by instead using the static isOsWindows method that already exists in AbstractClientAdapter.
>
> Before committing, we'll also want to externalize the strings and replace the e.printStackTrace lines with our standard error handling.

OK, thank you.

> But I've only seen the dialog by "tricking" it in debug, so I haven't really tested to see that it works. To really test, I'd need a server with certs. Do you have any advice for testing?
I think you know how to configure the server.
But on client side, it is necessary to have a java version > 1.6.0_u15 and you have to patch this or you have to use JACAPI from keyon (but it is licenced).
(SVNKit needs Revision > 6600).
So if you have any problem, just contact me.

> I assume the SVNKit check is because JavaHL does not support MSCAPI providers (do we know this for certain?)? It would be great if this feature could be extended to JavaHL.

At the moment only SVNKit supports this in version 1.3.2 Revision > 6600. So, this is not yet released on the homepage.
JavaHL: Here I think, that it works a little bit different. When I'm right JavaHL uses the dll's for communication. So the dll's should be build the right way and it should work with the openssl stuff.
Is this correct?
We have also build a svn command line client with supporting MS CAPI via openssl. I think JavaHL has to be build the same way, or?

------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1043&dsMessageId=2598743

To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_subclipse.tigris.org].
Received on 2010-04-29 13:05:34 CEST