Ruby or MRI: Matz Ruby Implementation, implemented in C. This is the original Ruby implementation
YARV: likely candidate of Ruby2.0
JRuby: Ruby implemented in Java IronRuby: Ruby implemented on a .net platform (on top of the CLR using the DLR)
Gardens Point Ruby.net: Ruby on a .net platform (on top of the CLR without using the DLR)
Cardinal: Ruby for the Parrot VM
MacRuby: Ruby 1.9 running directly on top of Mac OS X core technologies
MetaRuby: Ruby based implementation of Ruby, using ruby2c
Rubinius: Implementation of a Ruby VM almost entirely in Ruby
So, to answer your question - the original Ruby implementation is written in C, and JRuby is a ruby port in Java. If you needed to run Ruby on the JVM, or wanted to do so in order to have two-way communication between Ruby and Java - you'd use JRuby.
Dynamic languages like Ruby are most commonly used for specialized areas such as gluing other systems together; JRuby takes on this role in the Java world. For example, JRuby can pull data from one system, transform it and insert it into another. When the requirements change, modifying a JRuby script is as easy as changing a configuration file, thereby avoiding the complex compile-and-deploy cycle of Java integration code.
In addition to calling Java from Ruby, you can call Ruby from Java, making your application scriptable. With JRuby's minimal syntactic overhead, you can create an easy-to-use domain-specific language for users to work with (see "Creating DSLs with Ruby" by Jim Freeze). "
As Michael noted, JRuby is merely an implementation of the Ruby language on the JVM. So, effectively there is no difference, but as always, there will be "artifacts" between the two due to implementation details (f.e., threads perform better but behave a little differently in JRuby).
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com