Thomas E Enebo wrote:
So summary so far:
Problems:
A. Our stable branch is supported for Java 1.4 but jruby-openssl
required Java 5. Rails requires openssl.
B. Netbeans (and I presume any IDE which wants to bundle JRuby +
Rails) does not think it can distribute jruby-openssl gem.
1. Is this true based on recently discover bouncy castle FAQ entry
(http://bouncycastle.org/wiki/display/JA1/Frequently+Asked+Questions#FrequentlyAskedQuestions-9.WhatisBouncyCastle%27sexportclassificationintheUnitedStatesofAmerica%3F)
Solutions Proposed:
1. Build jruby-openssl with Java 1.4 and Java 5 (Bill thinks the
portions we need may work for 1.4)
No. Unless we divide it into one part using SSLEngine and one without it.
2. Monkey patch Rails in some way
i. Only implment possible portions of openssl which can be done
by Java itself
1. Ola thinks this is the path to hell fire
ii. Monkey patch Rails itself to provide an alternate default
cookie code (we need to hook this up somehow)
3. Beg...Cajole Rails core to make openssl an optional requirement for Rails 2.
At this point all options still seem reasonable to me. Either #2
options solve all problems but we need to understand the downsides.
Compiling to 1.4 is also a reasonable solution, but pending legal
clarification it may cause IDE's issues, so I think it is less
desirable than #2 options. #3 is the best for us, but it will not
help current Rails release and there is no guarantee we can convince
them that this is an issue they need to care about.
--
Ola Bini (http://ola-bini.blogspot.com)
JRuby Core Developer
Developer, ThoughtWorks Studios (http://studios.thoughtworks.com)
Practical JRuby on Rails (http://apress.com/book/view/9781590598818)
"Yields falsehood when quined" yields falsehood when quined.
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
