Forum: JRuby NameError: uninitialized constant Krypt::Provider::JDK with JRuby 1.7.12

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
E79e8520830d7695c1b80c9eeed84734?d=identicon&s=25 Ken E. (ken_e)
on 2014-04-29 21:44
After upgrading JRuby to 1.7.12 I get

NameError: uninitialized constant Krypt::Provider::JDK

when starting my application in WAS.

I noticed the release notes said bouncy-castle-java and krypt libraries
were unbundled from 1.7.12. Not sure what this means. My application
runs OK using WEBrick so clearly this is a packaging issue with WAS.

I tried adding krypt-core gem to my bundle file and that caused Warbler
to error with the same error.

I copied the krypt-core.jdk and kryptproviderjdk.jdk files to my lib
directory but no luck, same error with Warbler.

Any other ideas?
christian (Guest)
on 2014-04-29 22:25
(Received via mailing list)
did you use the krypt-0.0.2.rc1 gem and/or their jars ?
E79e8520830d7695c1b80c9eeed84734?d=identicon&s=25 Ken E. (ken_e)
on 2014-04-30 15:07
christian wrote in post #1144446:
> did you use the krypt-0.0.2.rc1 gem and/or their jars ?

I'm not sure how I should know I NEED this version.

Adding krypt-core to my Gem file seemed to be the right thing to do
however it pulled down version 0.0.1. Adding 0.0.2.rc1 as a version
didn't even work. I had to uninstall everything and manually install the
0.0.2.rc1 versions of krypt-core and krypt-provider-jdk using gem
install. Once I did that, Warbler worked and the WAR file started
successfully in WAS.

Thanks for your help.
christian (Guest)
on 2014-04-30 16:12
(Received via mailing list)
to see the default gems of jruby itself I use this:

GEM_PATH=bla jruby -S gem list -l

since these gems are "already" installed bundler does not install them.
This topic is locked and can not be replied to.