jruby-maven-plugins version 1.0.4
after a long time it reached 1.0.0 and got some more bug fixes already.
with those plugin you can run jruby with gem-artifacts, run tests
(junit,
minitest, rspec, cucumber) using those gems or pack them as embeded gems
into jar or war files
gem artifacts are offered by http://rubygems-proxy.torquebox.org/
some info can be found on jruby-wiki
-
JRuby scripting container packed as jar with embeded gems:
Jruby Scripting container using Gems with a Maven Project · jruby/jruby Wiki · GitHub -
JRuby scripting container inside a servlet packed as war:
JRuby Scripting container in Servlet using Gems packed with Maven · jruby/jruby Wiki · GitHub -
minitest, rspec, cucumber test for you ruby script:
Home · jruby/jruby Wiki · GitHub
all those pages use a Ruby-DSL for Maven
Ruby-Maven 3.1.1.0.8
basically a regular maven-3.1.1 installation with an extra thin wrapper
which “translates” a ruby file into a pom.xml
it comes with some “extras” feature to use a Gemfile, Jarfile or
gemspec-file as part of the POM. as well it leverages the
jruby-maven-plugins.
it also allows to execute code during a declared phase, i.e. like
inlined
maven plugins written in ruby.
Rubygems-Servlets
if you need Gem-Artifacts from your local rubygems repository you can
use
to proxy gem repository and deliver gem-artifacts.
for a more advanced solution use sonatype.org/nexus with
nexus-ruby-plugin
from:
GitHub - sonatype/nexus-ruby-support
rubygems-servlets uses the same core as this nexus-plugin.
JBundler 0.6.1
manage your jars for your ruby project with jbundler
- it uses ruby-maven now to lock down the version for the jars
- allows exclusions on jars (maven feature)
- uses jar-dependencies to “track and load” jars
the 0.6.x might break some existing project. in such a case please use
$ jbundle lock_down
instead of install and open an issue:
Jar-Dependencies 0.0.5
- during runtime it tracks the version of loaded jars - if
require_jar(…)
is used to load it - it can “vendor” the jars declared as “jar dependency” inside the
gemspec
file before packing them - it can “vendor” the jars when you install the gem
see on how you can manage your jars with jbundler (and
jar-dependencies):
Clueing Things Together
putting the Gemfile, Jarfile and some common maven-plugins, the
jruby-maven-plugins together. with the help of ruby-maven you can easily
pack
-
a rack application ready to deploy on servlet-container:
Rack Application with Ruby Maven · jruby/jruby Wiki · GitHub -
or deploy it on heroku
Rack Application with JBundler on Heroku · jruby/jruby Wiki · GitHub
LAST