jruby を Homebrew, apk, chocolatey, apt, MacPorts, Nix, pacman, scoop, dnf でインストール

プロジェクトリンク

• ホームページ
• リポジトリ
• 上流ドキュメント
• パッケージマネージャページ

コマンドとエイリアス

• ast
• install_doc
• jbundle
• jbundler
• jerb
• jgem
• jirb
• jirb_swing
• jminitest
• jracc
• jrake
• jrdoc
• jri
• jruby
• jruby.sh
• jrubyc
• jsyntax_suggest
• jtest-unit
• lock_jars

プロジェクトの歴史

JRuby began in 2001 as a Java-hosted Ruby implementation and became one of the canonical examples of a dynamic language on the JVM. The project moved from a direct-port style implementation toward a JVM-oriented runtime with Java integration, bytecode compilation work, and compatibility targets that followed major Ruby language versions.

The project's institutional story is unusually visible for an open-source language runtime. Charles Nutter and Thomas Enebo announced in September 2006 that Sun Microsystems hired them to work on JRuby full time. After Sun, JRuby development continued through Engine Yard and then Red Hat involvement, keeping paid core development behind the runtime for many years.

採用の歴史

JRuby became important during the Ruby on Rails expansion because it made Ruby applications plausible inside Java shops that already standardized on JVM operations. A 2011 JRuby blog post describes the 2006 JavaOne Rails demo as a turning point, at a time when the JVM language conversation centered on projects such as Jython and Groovy.

Package-manager adoption reflects that maturity: JRuby appears across Homebrew, Debian/Ubuntu, Fedora-style distributions, MacPorts, Chocolatey, Scoop, Nix, Arch, and Alpine. For package maintainers it is both a Ruby runtime and a Java application, so packaging has to account for Ruby executables, Java dependencies, and RubyGems-facing commands.

使われ方

JRuby is used to run Ruby applications on the JVM, embed Ruby scripting into Java systems, call Java libraries from Ruby, and package Ruby applications for environments where the JVM is the operational baseline. Its command set includes JRuby-prefixed versions of common Ruby tools such as gem, irb, rake, rdoc, and ri.

パッケージ好きにとっての重要性

JRuby is package-nerd catnip because it crosses ecosystem boundaries cleanly but not simply: Ruby code, Java bytecode, RubyGems, Maven-style expectations, native extension compatibility, and OS package managers all meet in one runtime. It is also a benchmark case for how language implementations survive outside their reference VM.

タイムライン

• 2001: JRuby project began as a Ruby implementation on the JVM.
• 2006: Sun Microsystems hired Charles Nutter and Thomas Enebo to work on JRuby full time.
• 2006: JRuby demonstrated Rails running on the JVM at JavaOne.
• 2009: JRuby core development moved from Sun to Engine Yard.
• 2012: Nutter and Enebo joined Red Hat to continue JRuby work.
• 2015: JRuby 9.0.0.0 moved the versioning line into Ruby 2.x compatibility.
• 2022: JRuby 9.4.0.0 targeted Ruby 3.1 compatibility.

Related projects

• Related projects include MRI/CRuby, RubyGems, Rails, Jython, Groovy, TruffleRuby, Rubinius, and JVM dynamic-language work such as invokedynamic.

ソース

• https://blog.headius.com/2006/09/jruby-steps-into-sun.html
• https://blog.jruby.org/2011/09/bringing-jruby-to-the-cloud
• https://formulae.brew.sh/formula/jruby
• https://github.com/jruby/jruby
• https://github.com/jruby/jruby/wiki/AboutJRuby
• https://www.jruby.org/
• https://www.jruby.org/documentation