Mark Phippard wrote:
> On Mon, Apr 6, 2009 at 7:28 PM, Ruslan Sivak <russ_at_vshift.com> wrote:
>
>> Mark Phippard wrote:
>>
>>> On Fri, Apr 3, 2009 at 4:11 PM, Ruslan Sivak <russ_at_vshift.com> wrote:
>>>
>>>
>>>
>>>> Thank you for your help. While that didn't exactly work, copying the
>>>> colabnet dll's into the plugin folder did.
>>>>
>>>> Is there a reason you don't build the SASL support into JavaHL?
>>>>
>>>>
>>> It can't be done in a way that'd work. The registry has to be updated
>>> to point to the SASL plugins you have installed. By using the
>>> CollabNet (or other) installer that part is taken care of.
>>>
>>>
>>>
>> Are you sure? It didn't work for me when I deleted the local dll's, but
>> did work when I copied all the ones from the collabnet folder. I guess
>> it's probably using the one from the collabnet folder for SASL, but is
>> it possible it just uses the one in the current folder instead?
>>
>
> It does not matter where it finds the DLL, as long as it can find the
> dependencies. The CollabNet binaries are compiled with Cyrus SASL and
> it will look in the registry to find the dynamic DLL modules it will
> use if needed. These are the parts we cannot deliver.
>
>
You can deliver the DLLs, and perhaps there could be a note in the
FAQ/README to add a registry entry with the proper path to the DLLs.
SASL is here to stay, and I can't imagine that a requirement to get it
to work properly is to install the Collabnet CLI binaries and then copy
the DLLs to the SubClipse folder.
>> In any case, how is SVNKit able to make it work?
>>
>
> SVNKit is using a Java implementation of SASL.
>
>
Is this a possibility for JavaHL?
------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=1598659
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2009-04-08 18:19:08 CEST