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
