On Dec 11, 2007, at 1:23 PM, Thomas E Enebo wrote:
Ok so I can put out a binary distro of 1.0.3 and in order for that to
be smooth I need to release an updated jruby-openssl. Here is the
problem (for windows):
1. Rails 2 requires openssl
2. JRuby 1.0.3 binary is compiled against Java 1.4 because that is
what we support
3. jruby-openssl is only supported using Java 1.5
4. jruby 1.0.3 binary will not run Rails 2
5. lack of profit!
So questions:
1. Would a 1.4 and 1.5 binary for 1.0.3 work? For people who want to
do Rails in 1.4 envs this sort of sucks. Plus it may not be too clear
what the issue is.
2. Is there any ways of making jruby-openssl work with Java 1.4? I
believe there are 1.4 BC jars?
3. Can we eliminate jruby-openssl as a req for Rails 2? Like monkey
patching in at least one place?
I think #3 would be really nice. Is it possible?
We're bundling JRuby and Rails with NetBeans, but we cannot bundle
openssl (legal headaches because of crypto and US export
restrictions). With Rails 1.2.5 this wasn't a problem - users who
want SSL can install it themselves, but it doesn't seem necessary for
basic functionality.
With Rails 2.0, you can't really do anything; as soon as you for
example try to run the rails code generator, it bombs out until you
go and fetch jruby openssl. This isn't very good for the out of the
box experience. I'd like to upgrade our bundled version to Rails 2.0
for NetBeans 6.1 but I'm not sure how to proceed. If the ssl stuff
could be made a bit more optional I can keep things the way they are
today.
I assume this is a Rails issue, but if we can do anything on our side
(even patching our bundled Rails 2.0 slightly) that would be great.
-- Tor
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
