The new format looks something like this:
War::Configuration.define do |config|
config.add_jetty_library('mysql-connector-java', '5.0.5')
config.add_jetty_library('jetty', '6.1.1', ['vendor/jetty'])
config.add_jetty_library('jetty-naming', '6.1.1', ['vendor/jetty'])
config.add_jetty_library('jetty-plus', '6.1.1', ['vendor/jetty'])
config.add_jetty_library('jetty-util', '6.1.1', ['vendor/jetty'])
config.add_jetty_library('servlet-api-2.5', '6.1.1', ['vendor/
jetty'])
config.add_jetty_library('start', '6.1.1', ['vendor/jetty']))
config.remove_gem('ActiveRecord-JDBC') # we already have this in
vendor
config.jetty_port = '8081' config.jetty_java_opts = "-Xmx512m" end(Btw, this is a neat way to remove dependency on a local maven repository. We simply check in the jar files so that our project is ready to run straight out of the Subversion repo.)
I've also added some sugar to add_jetty_library and add_java_library.This format is slightly more wordy than the previous one but it would be more familiar to Rails people as well as not requiring us to maintain a separate "DSL" class for every configuration option we would like to expose.
It is still fully backwards compatible but I think it would be a good idea to remove the previous DSL stuff as this completely supersedes it. I can update the example applications if people point out which one needs to be updated.
I think it would be a great idea to distribute all the jar files (jruby, jetty and maybe derby or a mysql driver) required to get a Rails application up and running with the plugin. We do want it to be zero effort to get Rails up and running with JRuby. (Which is currently not the case.) This would also completely remove the Maven dependency, Rails people will want to install Maven.
(Patch is taken from war-snapshot root.)
new_war_rb.patch
Description: Binary data
Cheers, Jon
_______________________________________________ Jruby-extras-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/jruby-extras-devel
