We are pleased to announce JRuby 0.9.0. This release has had so much
activity and progress that we decided to bump things up to a 0.9.0
release.
Many many bugs have been fixed to the point that:
-
RubyGems 0.9.0 installed and working*
-
WEBrick runs
-
Ruby on Rails runs on top of WEBrick (and generation scripts work)**
-
much improved YAML parser thanks to JvYAML and RbYAML projects
-
we bundle all non-native standard libraries in our distribution
We are getting to a correctness level where the more complicated Ruby
libraries and applications are running properly. From this point on we
are
going to improve on correctness and start to focus more on performance.For 0.9.1 we plan on getting Rails to run in a JEE servlet container
out
of the box. We also plan on improving Rake support. More correctness
fixes will be applied as discovered.As always we thank and encourage all who contribute to our project and
community. We would like to give some special thanks to: -
Ola B. for his rubygems and YAML work. He has spent a lot of sweat
and
tears to get rubygems functioning. His YAML work is a very exciting.
Development of JvYAML extends beyond JRuby in scope into the Java world
at large. He also spent a lot of time looking at bottlenecks and
addressing
performance of Rubygems once it was working. -
Evan Buswell for his server socket work. He improved on David
Corbin’s
original socket work and got the socket code working well enough to
WEBrick
to start.
footnotes:
- Though the YAML and download of the remote gem is somewhat comparable
to
Ruby performance we have a severe performance problem when generating
rdocs
for the new gem. We plan on looking at this at the beginning of the
next
development cycle. Consider using options: --no-rdoc and --no-ri
** We are able to generate and run the cookbook demo from rolling with
rails tutorial
(http://www.onlamp.com/pub/a/onlamp/2005/01/20/rails.html)
with what we have and all appears to work. With this said, it is likely
that there are several aspects of rails that are not working correctly.
See docs/README.rails for known issues/instructions in release.