I am saying with 1.7.1 you can add any version BC to you
classpath/classloader and use it, the jruby-openssl uses its own
version with different packages.

from you first post I had the feeling you use the java classes from BC
directly. if this is the case then I would say your code should work
with jruby-1.7.1 after you included the right BC jar.

- Kristian

On Fri, Jan 18, 2013 at 6:54 PM, Carl Bourne <carl.bou...@me.com> wrote:
> Kristian,
>
> Are you suggesting that should work in JRuby 1.7.1?
>
> Carl
>
> On 17 Jan 2013, at 04:17, kristian <m.krist...@web.de> wrote:
>
>> On Thu, Jan 17, 2013 at 3:32 AM, Matt Hauck <mattha...@gmail.com> wrote:
>>> Kristian, do you mean to say that jruby has forked BC and renamed all of its
>>> packages? I just unpacked the jar file in
>>> lib/ruby/shared/bcprov-jdk15-146.jar, and it doesn't look like any packages
>>> have been renamed.
>>
>> sorry I did not realize that this changed from 1.7.1 to 1.7.2
>> the package renaming took place during the packaging of the jruby.jar,
>> jruby-complete.jar and jruby-core.jar - this was really nice since it
>> did NOT force the BC version onto everybody - it was just an
>> implementation detail not visible to outside. the next version of BC
>> is coming and might come again with API changes.
>>
>> in the commit message headius mentioned something like problems with
>> signed security providers - not sure whether this is true for 1.7.1
>> since that was the reason to repackage BC in the first place. if there
>> were no problems with those signed security providers in 1.7.1 then I
>> think jruby-openssl should do embed BC and repackage it as jruby-1.7.1
>> - I am happy to help here. these wrapped jar as gems are quite a thing
>> when you want to embed jruby with java and need various gems which
>> wraps a jar which you might have already on your parent classloader.
>>
>> regards, Kristian
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to