Skip to content
Browse files

bundle update

  • Loading branch information...
1 parent 517fda2 commit fbe98495331ff584c00b8f3e9506160ad17eabaf @AE9RB committed Sep 26, 2011
View
4 Gemfile
@@ -16,5 +16,5 @@ gem 'warbler', '>= 1.3'
# jruby-rack embeds a specific version of rack
# keep in sync so the jar distribution has the correct docs
-gem 'jruby-rack', '= 1.0.9'
-gem 'rack', '= 1.2.2'
+gem 'jruby-rack', '= 1.0.10'
+gem 'rack', '= 1.3.2'
View
20 Gemfile.lock
@@ -1,21 +1,21 @@
GEM
remote: http://rubygems.org/
specs:
- haml (3.1.2)
- jruby-jars (1.6.2)
- jruby-rack (1.0.9)
+ haml (3.1.3)
+ jruby-jars (1.6.4)
+ jruby-rack (1.0.10)
kramdown (0.13.3)
maruku (0.6.0)
syntax (>= 1.0.0)
- minitest (2.3.1)
- rack (1.2.2)
- rake (0.8.7)
+ minitest (2.6.0)
+ rack (1.3.2)
+ rake (0.9.2)
rubyzip (0.9.4)
syntax (1.0.0)
- warbler (1.3.1)
+ warbler (1.3.2)
jruby-jars (>= 1.4.0)
jruby-rack (>= 1.0.0)
- rake (~> 0.8.7)
+ rake (>= 0.8.7)
rubyzip (>= 0.9.4)
yard (0.7.2)
@@ -25,11 +25,11 @@ PLATFORMS
DEPENDENCIES
haml
jruby-jars
- jruby-rack (= 1.0.9)
+ jruby-rack (= 1.0.10)
kramdown
maruku
minitest
- rack (= 1.2.2)
+ rack (= 1.3.2)
rake
warbler (>= 1.3)
yard
View
BIN vendor/cache/haml-3.1.2.gem
Binary file not shown.
View
BIN vendor/cache/haml-3.1.3.gem
Binary file not shown.
View
BIN vendor/cache/jruby-jars-1.6.2.gem → vendor/cache/jruby-jars-1.6.4.gem
Binary file not shown.
View
BIN vendor/cache/jruby-rack-1.0.10.gem
Binary file not shown.
View
BIN vendor/cache/jruby-rack-1.0.9.gem
Binary file not shown.
View
BIN vendor/cache/minitest-2.3.1.gem
Binary file not shown.
View
BIN vendor/cache/minitest-2.6.0.gem
Binary file not shown.
View
BIN vendor/cache/rack-1.2.2.gem
Binary file not shown.
View
BIN vendor/cache/rack-1.3.2.gem
Binary file not shown.
View
BIN vendor/cache/rake-0.8.7.gem
Binary file not shown.
View
BIN vendor/cache/rake-0.9.2.gem
Binary file not shown.
View
BIN vendor/cache/warbler-1.3.1.gem → vendor/cache/warbler-1.3.2.gem
Binary file not shown.

0 comments on commit fbe9849

Please sign in to comment.
Something went wrong with that request. Please try again.