Nutter was set to be full compliance with Ruby; the acid test of this compliance
would be running Rails unmodified. To set out on this project, many hours were devoted to
creating better test suites and reworking large parts of the system.
It was obvious from early on in this endeavor that it wouldn??™t be a good solution to just
port the C code straight off. There are large differences in the execution model of Java and C
programs, which means that it would be hard to duplicate the C structures when better
solutions were available in Java, and also that performance would be bad if trying to use an
execution model that looked like MRIs.
After porting several important extensions to Java (YAML, ZLib, and other important parts
of a Ruby system), both RubyGems and Rails started working. There were problems, but the
support improved by leaps and bounds. The story got even better when Tom and Charles got
hired by Sun Microsystems in September 2006 to work full time on JRuby.
Due to the great amount of tests that JRuby had, it was possible to do massive refactoring
of the code base, change much of the internals, and be confident that if the test suite ran, the
interpreter was good. The JRuby team has also been including test suites from other projects
into JRuby. The more notable of these tests are many of the regular Ruby implementation
tests, most of the tests from rubinius (another alternative implementation), and several application
suites. JRuby runs a continuous integration server where the full Rails test suite is run,
as well as RubyGems and Rake tests.
Pages:
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53