Mod. to #1 – you can void this by modifying the config.dirs element in the warble.rb file (in config dir.) to exclude the “lib” and “vendor” directories.

1) The “jruby -S warble” command will fail because it’s expecting a Rails project structure. You have to create a “lib” and a “vendor” directory in your project to enable the WAR creation task to finish.

2) This is a repeat of the Nick’s comment above – put config.webxml.booter = :merb to force the required changes to web.xml.

3) This was the tricky part. The jruby-rack.tld file embedded in the jruby-rack-0.9.1.jar file (which you will find in tmp/war/WEB-INF/lib/jruby-rack-0.9.1 after your first warble attempt) doesn’t validate and Websphere throws this weird ass GBean error. To fix it, you have to unpack the jruby-rack-0.9.1.jar file, and modify the META-INF/jruby-rack.tld file. You have to change the tagclass elements to be “tag-class” (don’t forget the closing tags), and then repack up the jruby-rack-0.9.1.jar file and place it in tmp/war/WEB-INF/lib. When you rerun “jruby -S warble” you should be able to deploy the WAR file (into Websphere at least).

- mongrel
- builder
- haml
- ruby2ruby

Thanks for the post!

config.webxml.booter = :merb

Which means you don’t need the step of copying web.xml, as Warbler will handle it for you.

I hope to make this step more automatic in the future by attempting to detect a Merb vs. Rails application.