lucidimagination-warbler 1.3.2.dev

data/Gemfile

@@ -0,0 +1,16 @@
+source "http://rubygems.org/"
+
+gem "rake", "~> 0.8.7"
+gem "rubyzip"
+gem "jruby-jars"
+gem "jruby-rack"
+
+group :development do
+  gem "jruby-openssl"
+  gem "rspec", "~> 1.3"
+  gem "diff-lcs"
+  gem "rcov", ">= 0.9.8"
+  gem "rubyforge"
+  gem "hoe", ">= 2.3.2"
+  gem "rdoc"
+end

data/History.txt

@@ -0,0 +1,217 @@
+== 1.3.1
+
+- Pin rake version to ~> 0.8.7 for now. Rake 0.9.0 compatibility will
+  follow in a future release.
+
+== 1.3.0
+
+- Warbler can now package regular Ruby projects as executable jar
+  files. See the README.txt file for details.
+- WARBLER-18: Heed BUNDLE_GEMFILE in environment
+- WARBLER-17: Allow config.excludes to work for files in public/
+- GH#3, #12, #17: Properly bundle when BUNDLE_PATH is set or
+  --deployment flag is used
+- JRUBY-5077, WARBLER-24: Gems from git repositories are now packaged
+  correctly
+- GH#20: Ruby 1.9.2 support
+- GH#8: Clean up compiled .class files after building war
+- GH#15: Simplify detection of thread-safe Rails
+
+== 1.2.1
+
+- Add --directoryListings=false to Winstone launch by default. In some
+  cases (sinatra) Winstone's directory listing masks application
+  content. (Fletcher Nichol)
+- Build and add META-INF/init.rb file into the war file. This is
+  recognized and loaded by JRuby-Rack 1.0.3 as a new way to do extra
+  environment initialization before the web framework is loaded. See
+  config.init_contents in Warbler::Config for details.
+
+== 1.2.0
+
+- Drop compatibility with earlier versions of Bundler -- Bundler has
+  changed a lot in a short period of time, so I'm expecting the number
+  of people depending on 0.8 or 0.9 to be small. Please use Warbler
+  1.2.0 with applications that depend on Bundler 1.0 or higher.
+- Support for Bundler groups. The 'development' and 'test' groups are
+  excluded by default.
+- Add 'compiled' feature: With this feature added to config.features
+  Warbler will pre-compile all Ruby files and will not ship the
+  original Ruby source in your war file.
+- warble.rb: Add config.bundle_without that controls Bundler groups to
+  be skipped, like 'Bundler.settings.without'.
+- warble.rb: Add config.compiled_ruby_files to specify which Ruby
+  files to compile when using the "compiled" feature. Defaults to
+  compiling all Ruby files.
+- warble.rb: Add config.gem_excludes which allows exclusion of some
+  gem files from the war. Default assumes no exclusions.
+- Exclude 'tmp/war' directory so that people upgrading from 0.9 won't
+  accidentally include it in their war file.
+
+== 1.1.0
+
+- Add concept of "features" -- small Rake tasks that run before the
+  creation of the war file and make manipulations to the war file
+  structure.
+- Add 'gemjar' feature: Bundle all gems into a gems.jar to reduce the
+  number of files in the archive (mostly useful for Google AppEngine).
+  Usage: run "warble gemjar war" or set config.features = %w(gemjar) in
+  warble.rb to use this feature.
+- Add 'executable' feature: Bundle an embedded web server in the war
+  file so that the entire application can be run as
+  'java -jar myapp.war'.
+  Usage: run "warble executable war" or set config.features = %w(executable)
+  in warble.rb to use this feature.
+  To see embedded webserver options, add '--help' to the 'java -jar'
+  command line.
+- No longer embed config.ru in web.xml as 'rackup' parameter by
+  default. Instead, config.ru is included in the war file.
+- Bump jruby-rack version requirement to 0.9.8.
+
+== 1.0.3
+
+- Tracking recent Bundler changes - handle locked Gemfiles differently
+  than unlocked ones
+- Handle file-based symlinks, and warn about inoperational directory
+  symlinks under non-JRuby versions of Ruby.
+
+== 1.0.2
+
+- Add 'warble pluginize' task back. This task now just creates a
+  vendor/plugins/warbler/tasks/warbler.rake file. There's no need to
+  "vendor" all of Warbler into your application anymore.
+
+== 1.0.1
+
+- Fix careless bug where Warbler doesn't work with JRuby 1.4
+
+== 1.0
+
+- Warbler hits 1.0! There are enough structural changes in Warbler
+  that I feel it's time to roll the major version over to 1.0.
+- Add support for Bundler. Detect Gemfiles, make sure gems are
+  included in the war file and rewrite .bundle/environment.rb inside
+  the war file.
+- Warbler now uses RubyZip to create the war file in-place, without
+  copying files to a tmp/war staging area. When run in JRuby it uses a
+  Java ZipOutputStream for a modest performance boost.
+- Add config option to allow override of gem_home (Daniel Harrington).
+- Stop bundling jruby-rack, as promised.
+- WARBLER-3: don't add from Rails config.gems if they are frozen
+- WARBLER-7: Add config.webinf_files option with more support for
+  custom web.xml files
+
+== 0.9.14
+
+- So, jruby-rack is bundled for one more release. 1.0 will not contain
+  any jar files, I promise!
+- Upgraded jruby-rack to 0.9.5.
+- Unbundled jruby-complete jar in favor of new jruby-jars gem, which
+  can be upgraded separately.
+- Skip gems which have no loaded_from attribute set
+  (this happened with the Authlogic gem on Edge Rails)
+  (thanks Laszlo Bacsi)
+
+== 0.9.13
+
+- RailsConf 2009 edition.
+- Only bundled JRuby and JRuby-Rack upgrades. Bug fixes will have to come in 0.9.14.
+- This should also be the last release with bundled JRuby and JRuby-Rack.
+- Upgrade to JRuby 1.3.0RC1 and JRuby-Rack 0.9.4. The latter allows 
+  Rails 2.3 to work with Warbler.
+
+== 0.9.12
+
+- Allow framework auto-detection to be disabled. Set
+  `Warbler.framework_detection = false' at the top of config/warble.rb
+  or uncomment the line from a newly generated config.
+- Add configuration option to set manifest file (thanks Tommy McGuire)
+- Mitigate RubyGems 1.3 compatibility issue (thanks Jens Norrgrann)
+- Add experimental `war:exploded` task. This allows you to deploy your
+  application in an exploded mode, thus allowing continual development
+  without re-warring and re-deploying. Feedback is appreciated if you
+  try this feature; it may not work in all application servers and for
+  applications other than Rails.
+- Handle Rails gem dependencies better (thanks Laszlo Bacsi)
+- Auto-detect Merb dependencies (Merb >= 1.0 only). Please give
+  feedback if you try Warbler with a Merb 1.0 app.
+- Ignore gem development dependencies
+- Upgrade to JRuby 1.1.6 and JRuby-Rack 0.9.3
+
+== 0.9.11
+
+- Auto-detect Rails and Merb and configure appropriately
+  - For Rails, set rails booter, determine max runtimes based on Rails.configuration.threadsafe!,
+    add Rails gem, detect Rails version, set gems to be packaged based on
+    Rails.configuration.gems if available
+  - Rails gems only added if Rails application detected
+  - For Merb, set merb booter automatically
+- Auto-detect config.ru rackup script and pass it into config.webxml.rackup
+- rails.env now commented by default in config/warble.rb and internally default
+  the value to 'production'
+- Default directories in config.dirs to only those that are found to be present
+- Allow config.gems array to contain regexps and Gem::Dependency objects as well
+ (assist from Jani Soila)
+- Fix bug ensuring you can += and -= for config.gems
+- Upgrade to JRuby 1.1.4 and JRuby-Rack 0.9.2
+- add [] as a way to specify non-identifier keys, example: config.webxml['!@#$%^'] = 'haha'
+
+== 0.9.10
+
+- Upgraded to JRuby-Rack 0.9.1. Fixes JRUBY-2620, JRUBY-2594, JRUBY-2507.
+- Now verified to work with Camping and Sinatra. See
+  http://github.com/nicksieger/jruby-rack/tree/master/examples for examples
+  of how to configure Warbler to package your Camping and Sinatra apps.
+- Upgraded to JRuby 1.1.3.
+- Log files are no longer packaged in the .war file.
+- Fix #<Warbler::WebxmlOpenStruct ...> appearing in web.xml and document workarounds.
+- Add config.autodeploy_dir that, when specified, will create the war there.
+
+== 0.9.9
+
+- Now shipping with JRuby-Rack 0.9!
+- Upgrade to JRuby 1.1.1
+- warble.rb and web.xml.erb have changed as a result of the change to JRuby-Rack -- we
+  recommend comparing the new base copies with any existing configuration you have to
+  make sure you pick up the differences.
+- Config changes:
+-- config.webxml.booter chooses what kind of application to use (:rails, :merb or plain :rack).
+-- config.webxml.pool.* have been replaced by config.webxml.jruby.(min|max).runtimes
+-- config.webxml.standalone and config.webxml.jruby_home no longer have any effect.
+
+== 0.9.5
+
+- Fix bug in plugin warbler.rake task file that would favor loading warbler from gems before the version
+  installed as a plugin
+- Upgrade to JRuby 1.1 final and Goldspike 1.6.1
+
+== 0.9.4
+
+- Update bundled JRuby to 1.1RC3 and Goldspike to 1.6.
+- Fix inclusion of gems with platform-specific bits (e.g., Hpricot)
+
+== 0.9.3
+
+- Update bundled JRuby to 1.1RC2, and Goldspike to 1.5.
+- The bundled JRuby and Goldspike now require JDK 5 or greater. If you wish to use JDK 1.4, use Warbler 0.9.2.
+
+== 0.9.2
+
+- Update bundled JRuby to version 1.0.3 and Goldspike 1.4.
+- Add config.java_classes to allow you to copy loose Java classes into WEB-INF/classes.
+- Make jar command a single command string so that jar creation doesn't fail (works around bug in JRuby 1.0.2)
+- Use File.join to form staging directory, should produce the proper jar-command path in Windows
+
+== 0.9.1
+
+- Add rake >= 0.7.3 as a dependency in the gem specification.
+- Add debug tasks: war:debug, war:debug:gems, war:debug:public, war:debug:app, war:debug:includes,
+  war:debug:excludes, war:debug:java_libs gives you a breakdown of what Warbler expects to package.
+
+== 0.9
+
+- Birthday! Warbler is a gem to make a .war file out of a Rails project. The intent is to provide a
+  minimal, flexible, ruby-like way to bundle up all of your application files for deployment to a
+  Java application server.
+- Bundled versions: goldspike-1.4-SNAPSHOT and jruby-complete-1.0.1
+- Works as both a gem (rake application) or a plugin

data/LICENSE.txt

@@ -0,0 +1,26 @@
+= Warbler
+
+Warbler is provided under the terms of the MIT license.
+
+Warbler (c) 2010-2011 Engine Yard, Inc.
+Warbler (c) 2007-2009 Sun Microsystems, Inc.
+
+Permission is hereby granted, free of charge, to any person
+obtaining a copy of this software and associated documentation files
+(the "Software"), to deal in the Software without restriction,
+including without limitation the rights to use, copy, modify, merge,
+publish, distribute, sublicense, and/or sell copies of the Software,
+and to permit persons to whom the Software is furnished to do so,
+subject to the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS
+BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN
+ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
+CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

data/Manifest.txt

@@ -0,0 +1,92 @@
+Gemfile
+History.txt
+LICENSE.txt
+Manifest.txt
+README.txt
+Rakefile
+bin/warble
+ext/JarMain.java
+ext/WarMain.java
+ext/WarblerJar.java
+ext/WarblerJarService.java
+lib/warbler
+lib/warbler.rb
+lib/warbler/application.rb
+lib/warbler/config.rb
+lib/warbler/gems.rb
+lib/warbler/jar.rb
+lib/warbler/task.rb
+lib/warbler/templates
+lib/warbler/templates/bundler.erb
+lib/warbler/templates/config.erb
+lib/warbler/templates/jar.erb
+lib/warbler/templates/rack.erb
+lib/warbler/templates/rails.erb
+lib/warbler/templates/war.erb
+lib/warbler/traits
+lib/warbler/traits.rb
+lib/warbler/traits/bundler.rb
+lib/warbler/traits/gemspec.rb
+lib/warbler/traits/jar.rb
+lib/warbler/traits/merb.rb
+lib/warbler/traits/nogemspec.rb
+lib/warbler/traits/rack.rb
+lib/warbler/traits/rails.rb
+lib/warbler/traits/war.rb
+lib/warbler/version.rb
+lib/warbler/war.rb
+lib/warbler_jar.jar
+spec/drb_helper.rb
+spec/sample_bundler/Gemfile.lock
+spec/sample_bundler/config.ru
+spec/sample_bundler/vendor/bundle/jruby/1.8
+spec/sample_bundler/vendor/bundle/jruby/1.8/cache/rake-0.8.7.gem
+spec/sample_bundler/vendor/bundle/jruby/1.8/gems/rake-0.8.7
+spec/sample_bundler/vendor/bundle/jruby/1.8/gems/rake-0.8.7/lib/rake.rb
+spec/sample_bundler/vendor/bundle/jruby/1.8/specifications/rake-0.8.7.gemspec
+spec/sample_bundler/vendor/bundle/ruby/1.8
+spec/sample_bundler/vendor/bundle/ruby/1.8/cache/rake-0.8.7.gem
+spec/sample_bundler/vendor/bundle/ruby/1.8/gems/rake-0.8.7
+spec/sample_bundler/vendor/bundle/ruby/1.8/gems/rake-0.8.7/lib/rake.rb
+spec/sample_bundler/vendor/bundle/ruby/1.8/specifications/rake-0.8.7.gemspec
+spec/sample_bundler/vendor/bundle/ruby/1.9.1
+spec/sample_bundler/vendor/bundle/ruby/1.9.1/cache/rake-0.8.7.gem
+spec/sample_bundler/vendor/bundle/ruby/1.9.1/gems/rake-0.8.7
+spec/sample_bundler/vendor/bundle/ruby/1.9.1/gems/rake-0.8.7/lib/rake.rb
+spec/sample_bundler/vendor/bundle/ruby/1.9.1/specifications/rake-0.8.7.gemspec
+spec/sample_jar/History.txt
+spec/sample_jar/Manifest.txt
+spec/sample_jar/README.txt
+spec/sample_jar/lib/sample_jar.rb
+spec/sample_jar/sample_jar.gemspec
+spec/sample_jar/test/test_sample_jar.rb
+spec/sample_war/app/controllers/application.rb
+spec/sample_war/app/helpers/application_helper.rb
+spec/sample_war/config/boot.rb
+spec/sample_war/config/database.yml
+spec/sample_war/config/environment.rb
+spec/sample_war/config/environments/development.rb
+spec/sample_war/config/environments/production.rb
+spec/sample_war/config/environments/test.rb
+spec/sample_war/config/initializers/inflections.rb
+spec/sample_war/config/initializers/mime_types.rb
+spec/sample_war/config/initializers/new_rails_defaults.rb
+spec/sample_war/config/routes.rb
+spec/sample_war/lib/tasks/utils.rake
+spec/sample_war/public/404.html
+spec/sample_war/public/422.html
+spec/sample_war/public/500.html
+spec/sample_war/public/favicon.ico
+spec/sample_war/public/index.html
+spec/sample_war/public/robots.txt
+spec/spec_helper.rb
+spec/warbler/application_spec.rb
+spec/warbler/bundler_spec.rb
+spec/warbler/config_spec.rb
+spec/warbler/gems_spec.rb
+spec/warbler/jar_spec.rb
+spec/warbler/task_spec.rb
+spec/warbler/traits_spec.rb
+spec/warbler/war_spec.rb
+warble.rb
+web.xml.erb

data/README.txt

@@ -0,0 +1,255 @@
+= Warbler
+
+Warbler is a gem to make a Java jar or war file out of any Ruby,
+Rails, Merb, or Rack application. Warbler provides a minimal,
+flexible, Ruby-like way to bundle up all of your application files for
+deployment to a Java environment.
+
+Warbler provides a sane set of out-of-the box defaults that should allow most
+Ruby applications to assemble and Just Work.
+
+== Getting Started
+
+1. Install the gem: <tt>gem install warbler</tt>.
+2. Run warbler in the top directory of your application: <tt>warble</tt>.
+3a. For a web project, deploy your myapp.war file to your favorite Java
+    application server.
+3b. For a standalone applications, just run it: <tt>java -jar myapp.jar</tt>.
+
+== Usage
+
+Warbler's +warble+ command is just a small wrapper around Rake with internally
+defined tasks.
+
+    $ warble -T
+    warble compiled    # Feature: precompile all Ruby files
+    warble config      # Generate a configuration file to customize your archive
+    warble executable  # Feature: make an executable archive
+    warble gemjar      # Feature: package gem repository inside a war
+    warble pluginize   # Install Warbler tasks in your Rails application
+    warble version     # Display version of Warbler
+    warble war         # Create the project war file
+    warble war:clean   # Remove the project war file
+    warble war:debug   # Dump diagnostic information
+
+Type <tt>warble</tt> to create the jar or war file.
+
+== Features
+
+Warbler "features" are small Rake tasks that run before the creation
+of the war file and make manipulations to the archive structure. For
+instance, the +executable+ feature makes your war file capable of
+running on its own, without a servlet container:
+
+    warble executable war
+
+You can either add features to the warbler command line:
+
+    warble FEATURE war
+
+or configure them in config/warble.rb to always be used.
+
+   config.features = %w(FEATURE)
+
+Currently, three features are available.
+
+* +gemjar+: This bundles all gems into a single gem file to reduce the
+  number of files in the .war. This is mostly useful for Google
+  AppEngine where the number of files per application has a limit.
+  (Note: not applicable for jar-based applications.)
+* +executable+: This bundles an embedded web server into the .war so
+  that it can either be deployed into a traditional java web server or
+  run as a standalone application using <tt>java -jar myapp.war</tt>.
+  (Note: jar-based applications are executable by default.)
+* +compiled+: This uses +jrubyc+ to precompile all .rb files in your
+  application to .class files and includes those in the .war instead
+  of the Ruby sources.
+
+Features may form the basis for a third-party plugin system in the
+future if there is demand.
+
+== War or Jar?
+
+War-based projects are for Rails, Merb, or Rack-based web
+applications. They usually contain a <tt>config/environment.rb</tt>
+file, a <tt>config/init.rb</tt> file, or a <tt>config.ru</tt> file.
+The presence of these files are used to determine if the project
+is a web application, and thus a Java EE compatible war file is built
+for the project.
+
+Jar-based projects are for standalone Ruby applications. Usually a
+Ruby application has a launcher script in the <tt>bin</tt> directory
+and Ruby code in the <tt>lib</tt> directory. Warbler packages the
+application so that <tt>java -jar myapp.jar</tt> runs the launcher
+script.
+
+== Jar Files
+
+=== Gem Specification (gemspec) Files
+
+If your project has a <tt>.gemspec</tt> file in the top directory, it
+will be used to configure the project's dependencies, launcher script,
+require paths, and the files to be included in the archive. For best
+results make sure your gemspec specifies all of the following
+attributes:
+
+* +executables+
+* +require_paths+
+* runtime dependencies added with +add_dependency+
+
+If your project do not have a <tt>.gemspec</tt>, Warbler will attempt
+to guess the launcher from the contents of the <tt>bin</tt> directory
+and use the <tt>lib</tt> directory as the lone require path. All files
+in the project will be included in the archive.
+
+=== Bundler
+
+Applications that use Bundler[http://gembundler.com/], detected via
+presence of a +Gemfile+, will have the gems packaged up into the
+archive along with the Gemfile. The Bundler groups named
++:development+ and +:test+ will be excluded by default, unless you
+specify with +config.bundle_without+ in +config/warble.rb+.
+
+Warbler supports Bundler for gems and git repositories, but not for
+plain path components. Warbler will warn when a +:path+ component is
+found in the +Gemfile+ and will refuse to include it in the archive.
+
+== War Files
+
+=== Rails applications
+
+Rails applications are detected automatically and configured appropriately.
+The following items are set up for you:
+
+* Your application runs in the +production+ environment by default.
+Change it in <tt>config/warble.rb</tt> (see below).
+* The Rails gem is packaged if you haven't vendored Rails (Rails <= 2.x).
+* Other gems configured in Rails.configuration.gems are packaged
+(Rails 2.1 - 2.3)
+* Multi-thread-safe execution (as introduced in Rails 2.2) is detected
+and runtime pooling is disabled.
+
+=== Merb applications
+
+Merb applications are detected automatically, and the merb-core gem and its
+dependencies are packaged.
+
+=== Other Rack-based applications
+
+If you have a +config.ru+ file in the top directory or one of the
+immediate subdirectories of your application, it will be included and
+used as the rackup script for your Rack-based application. You will
+probably need to specify framework and application gems in
+config/warble.rb unless you're using Bundler to manage your gems.
+<tt>ENV['RACK_ENV']</tt> will be set to +production+.
+
+See {the examples in the jruby-rack project}[http://github.com/nicksieger/jruby-rack/tree/master/examples/]
+of how to configure Warbler to package Camping and Sinatra apps.
+
+=== Configuration auto-detect notes
+
+* Warbler will load the +environment+ Rake task in a Rails application
+  to try to detect some configuration. If you don't have database
+  access in the environment where you package your application, you
+  may wish to set +Warbler.framework_detection+ to false at the top of
+  config.rb. In this case you may need to specify additional details
+  such as booter, gems and other settings that would normally be
+  gleaned from the application configuration.
+* A more accurate way of detecting a Merb application's gems is
+  needed. Until then, you will have to specify them in
+  +config/warble.rb+. See below.
+* Is it possible to more generally detect what gems an application
+  uses? Gem.loaded_specs is available, but the application needs to be
+  loaded first before its contents are reliable.
+
+== Custom configuration
+
+If the default settings are not appropriate for your application, you can
+customize Warbler's behavior. To customize files, libraries, and gems included
+in the .war file, you'll need a config/warble.rb file. There a two ways of
+doing this. With the gem, simply run
+
+    warble config
+
+Finally, edit the config/warble.rb to your taste. The generated
+config/warble.rb file is fully-documented with the available options
+and default values.
+
+=== War layout
+
+The default configuration puts application files (+app+, +config+, +lib+,
++log+, +vendor+, +tmp+) under the .war file's WEB-INF directory, and files in
++public+ in the root of the .war file. Any Java .jar files stored in lib will
+automatically be placed in WEB-INF/lib for placement on the web app's
+classpath.
+
+=== Web.xml
+
+Java web applications are configured mainly through this file, and Warbler
+creates a suitable default file for you for use. However, if you need to
+customize it in any way, you have two options.
+
+1. If you just want a static web.xml file whose contents you manually
+   control, you may unzip the one generated for you in
+   <tt>yourapp.war:WEB-INF/web.xml</tt> to <tt>config/web.xml</tt> and
+   modify as needed. It will be copied into subsequent copies of the
+   war file for you.
+2. If you want to inject some dynamic information into the file, copy
+   the <tt>WARBLER_HOME/web.xml.erb</tt> to
+   <tt>config/web.xml.erb</tt>. Its contents will be evaluated for you
+   and put in the webapp. Note that you can also pass arbitrary
+   properties to the ERb template by setting
+   <tt>config.webxml.customkey</tt> values in your
+   <tt>config/warble.rb</tt> file.
+
+For more information on configuration, see Warbler::Config.
+
+== Rakefile integration
+
+If you'd like to control Warbler from your own project's Rakefile,
+simply add the following code somewhere in the Rakefile:
+
+    require 'warbler'
+    Warbler::Task.new
+
+If you're using Bundler, you'll want to add Warbler to your Gemfile:
+
+    group :development do
+      gem "warbler"
+    end
+
+Now you should be able to invoke "rake war" to create your war file.
+
+== Troubleshooting
+
+If Warbler isn't packaging the files you were expecting, use the
++war:debug+ task to give you more insight into what's going on.
+
+If you think you found a bug, please file one at
+http://kenai.com/jira/browse/WARBLER.
+
+== Source
+
+You can get the Warbler source using Git, in any of the following ways:
+
+   git clone git://git.caldersphere.net/warbler.git
+   git clone git://github.com/nicksieger/warbler.git
+   git clone git://kenai.com/warbler~main
+
+You can also download a tarball of Warbler source at
+http://github.com/nicksieger/warbler/tree/master.
+
+== Development
+
+You can develop Warbler with any implementation of Ruby. To write
+Warbler code and run specs, you need to have Bundler installed
+and run "bundle install" once.
+
+After that, simply run "rake".
+
+== License
+
+Warbler is provided under the terms of the MIT license.
+
+Warbler (c) 2010-2011 Engine Yard, Inc.
+Warbler (c) 2007-2009 Sun Microsystems, Inc.