Thanks for the explanation Kristian! In the meantime, can anybody suggest a workaround to this issue?
Regards, Carl On 20 Jan 2013, at 18:17, kristian <m.krist...@web.de> wrote: > the BC version is bound to jruby-openssl gem. whenever you use that > gem is depends on a BC gem, i.e. it loads the BC jars into the jruby > classloader. currently this BC gem wraps BC-1.46 jaar and soon there > will be a jruby-openssl gem which will depend on another wrapped BC > version. jruby-1.7.1 was nice in the sense that BC was hidden and had > no impact on the jruby client code with regard to the version of BC - > as you are doing it right now. > > there are other gems which just loads up a couple of jars in the > jruby-classloader which are packed within the gem. it is kind of > difficult to find out what versions of those jar are used and even > what jars they are using. I personally miss something to tell the > jruby classloader NOT to load any jars since the parent classloader > provides everything (the java way of adding jars). in that sense scala > or/and groovy might integrate smoother with java then jruby does. > > personally still prefer jruby over groovy or scala and hope there will > be one day a nice solution for jruby how to use gems and jars equal > manner. > > regards, > Kristian > > > On Sun, Jan 20, 2013 at 10:54 PM, Carl Bourne <carl.bou...@me.com> wrote: >> I'm confused! >> >> Does this mean from now on if I use a version of JRuby later than 1.7.1 I >> can't use the latest 1.4.7 Bouncy Castle libs? >> >> So my code seems to work fine with JRuby 1.7.1 but not JRuby 1.7.2! >> >> Could somebody please explain whats happening here as I seem to be going >> round in circles and wasting hours of my time on something that I was hoping >> to be straight forward. After all, one of the main benefits of JRuby is that >> it can reference existing Java libs! >> >> Should I be looking at a language that has better interoperability with Java >> like Scala or Groovy, or should I persevere ? >> >> >> Best Regards, >> >> Carl >> >> >> On 19 Jan 2013, at 03:49, kristian <m.krist...@web.de> wrote: >> >> Still think jruby-openssl should hide its BC the same way as jruby1.7.1 is >> doing. The way these gems include jar dependencies is very problematic in >> many ways. >> >> Regards Kristian >> >> Am 18.01.2013 22:50 schrieb "Carl Bourne" <carl.bou...@me.com>: >>> >>> OK - So to be clear, JRuby 1.7.2 or greater includes BC-1.47 within its >>> jruby-openssl gem? >>> >>> So the DERObjectIdentifier and other BC-1.47 methods should be available? >>> >>> Regards, >>> >>> Carl >>> >>> >>> On 18 Jan 2013, at 16:38, kristian <m.krist...@web.de> wrote: >>> >>>> I am not sure how much you are using the BC-1.47 specific API, maybe >>>> your code works with BC-1.46 as well. >>>> >>>> anyways t looks like jruby-1.7.1 will be the only jruby where you can >>>> choose the version of BC yourself. >>>> >>>> - Kristian >>>> >>>> >>>> On Fri, Jan 18, 2013 at 9:57 PM, kristian <m.krist...@web.de> wrote: >>>>> On Fri, Jan 18, 2013 at 9:49 PM, Carl Bourne <carl.bou...@me.com> >>>>> wrote: >>>>>> Do you know if these issues will be resolved with JRuby 1.7.3 or later >>>>>> ? >>>>> >>>>> as far understand the moment the jruby-openssl gem uses the BC-1.47 >>>>> your code run with that gem as well. >>>>> >>>>> - Kristian >>>>> >>>>> PS glad that I could help . . . >>>> >>>> --------------------------------------------------------------------- >>>> 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 > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
