On Apr 28, 2012 1:00 PM, "Nick Sieger" wrote:
> Yeah, as a stopgap we could still compile against BC but just blow up if
the jars are not available, and they could work again simply by "gem
install bouncy-castle-java".
>
> /Nick
Yeah I have been thinking the same thing, probably using a post-inst
On Apr 28, 2012, at 10:40 AM, Charles Oliver Nutter wrote:
> This does bring up a logistical issue...there are folks who will not
> want to touch a JRuby distribution with BC included, so it's likely
> that we'll need to provide artifacts that omit BC completely. That
> means we'll still ideally
A most gleeful +1 from me.
/Nick
On Apr 26, 2012, at 11:50 PM, Charles Oliver Nutter wrote:
> Ok, we need to discuss this a bit. I think it's time we rolled
> jruby-ossl (OpenSSL) directly into JRuby and maintained it there.
>
> There are many reasons why this will make life easier:
>
> * No re
I think the only concern we have ever had is the legality. If we can
be reasonably sure this is legal then I don't know why anyone would
complain (perhaps jar size?)...
-Tom
On Thu, Apr 26, 2012 at 11:50 PM, Charles Oliver Nutter
wrote:
> Ok, we need to discuss this a bit. I think it's time we
On Apr 27, 2012, at 12:50 AM, Charles Oliver Nutter wrote:
> Ok, we need to discuss this a bit. I think it's time we rolled
> jruby-ossl (OpenSSL) directly into JRuby and maintained it there.
>
> There are many reasons why this will make life easier:
>
> * No requirement to install a gem to get
Ok, we need to discuss this a bit. I think it's time we rolled
jruby-ossl (OpenSSL) directly into JRuby and maintained it there.
There are many reasons why this will make life easier:
* No requirement to install a gem to get SSL support, which is
sometimes impossible of only SSL sources are avail
