ruboto 0.15.0 → 0.16.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: c968343b3a48179ec48fecd316b53fa63ad49e49
-  data.tar.gz: 2a00ac4f9378a4ea037519665d94dee920b0b076
+  metadata.gz: 4fb13ffa79e6bb330307b86180514990fcef5fc8
+  data.tar.gz: f1f984e01bbc611d45edfbc6405bd160c6f80631
 SHA512:
-  metadata.gz: 7beb90cd29d1041a36f2d657023dafc8ac6869ab94532eef8123dddd00fac65f7695747914b0b1549b30284cc9036167545f35c428d3d21637c8bc7f00f52ca2
-  data.tar.gz: ca14e4d1b2bb0c2a49f809b5211e476deb03a4630d55b3aee0109afb2b19f2c2b8f008d63e10f4e760ef41fbca0f4d3aa205113dd4098c0ac3d195eeec356bab
+  metadata.gz: ab88a4c19b913cc21b5f8c71960c331ffcee29f329a50b5107b5003cb9ba69ca219a3692267fa2b8a92d4fe22bfb42d04353a1bbdb0ae6c98436dbbd79086721
+  data.tar.gz: 54e0b680d1f1d6fa9ab05803dcc620d73bd766c84d01061a18eca543e7f0baf3befb19496c9cda49287ea535191d635517bfef351bc0dbbf1a828c9dd2c6734e

data/Gemfile.lock

@@ -1,9 +1,10 @@
 PATH
   remote: .
   specs:
-    ruboto (0.15.0)
+    ruboto (0.16.0)
       main (>= 4.7.2)
       rake
+      rubyzip (>= 1.0.0)
 
 GEM
   remote: http://rubygems.org/
@@ -18,8 +19,10 @@ GEM
       map (>= 5.1.0)
     map (6.5.1)
     rake (10.1.0)
+    rubyzip (1.0.0)
 
 PLATFORMS
+  java
   ruby
 
 DEPENDENCIES

data/README.md

@@ -56,10 +56,10 @@ version (api-level) of Android.
 Command-line Tools
 -------
 
-* [Application generator](#application_generator) (like the rails application generator)
+* [Application generator](#application_generator) (like the Rails application generator)
 * [Class generator](#class_generator) to generate additional Activities, BroadcastReceivers, Services, etc.
-* [Callback generator](#class_generator) to generate specific subclasses to open up access (callbacks) for various portions of the Android API.
-* [Packaging task](#packaging_task) to generate an apk file
+* [Callback generator](#class_generator) to generate specific subclasses to open up access (callbacks) for various portions of the Android API
+* [Packaging task](#packaging_task) to generate an .apk file
 * [Release task](#release_task) to deploy a generated package to an emulator or connected device
 * [Develop without having to compile to try every change](#update_scripts)
 
@@ -68,38 +68,39 @@ Command-line Tools
 ### Application generator
 
     $ ruboto gen app --package com.yourdomain.whatever --path path/to/where/you/want/the/app --name NameOfApp --target android-version --min-sdk another-android-version --activity MainActivityName
-Version values must be specified using'android-' and the sdk level number (e.g., android-10 is gingerbread).
+Version values must be specified using `android-` and the sdk level number (e.g., android-10 is Gingerbread.)
 
 <a name="class_generator"></a>
 ### Class generator
 
-Generates a Java class (Activity, Service, or BroadcastReceiver) associated with a specific ruboto script.  The generator also generates a corresponding test script.
+Generates a Java class (Activity, Service, or BroadcastReceiver) associated with a specific Ruboto script.  The generator also generates a corresponding test script.
 
     $ ruboto gen class ClassName --name YourObjectName
-Ex:
+For example:
+
     $ ruboto gen class BroadcastReceiver --name AwesomenessReceiver
 
 <a name="callback_generator"></a>
 ### Callback generator
 
-You can subclass any part of the Android API to pass control over to a script when the specified methods are called. You can also create classes that implement a single Android interface to pass control over to ruboto.
+You can subclass any part of the Android API to pass control over to a script when the specified methods are called. You can also create classes that implement a single Android interface to pass control over to Ruboto.
 
 Starting with Ruboto 0.6.0 there are easy ways to do this within your scripts.
-The new way of generating interfaces and subclasses is described in the wiki
+The new way of generating interfaces and subclasses is described in the wiki page
 [Generating classes for callbacks](https://github.com/ruboto/ruboto/wiki/Generating-classes-for-callbacks).
 
 <a name="packaging_task"></a>
 ### Packaging task
 
-This will generate an apk file.
+This will generate an .apk file:
 
     $ rake debug
 
-To generate an apk and install it to a connected device (or emulator) all in one go, run
+To generate an .apk and install it to a connected device (or emulator) all in one go, run:
 
     $ rake install
 
-To start the installed app, run
+To start the installed app, run:
 
     $ rake start
 
@@ -122,7 +123,7 @@ Also make sure to keep your key backed up (if you lose it, you won't be able to
 release updates to your app that can install right over the old versions), but
 secure.
 
-Now get that `.apk` to the market!
+Now get that .apk to the market!
 
 <a name="update_scripts"></a>
 ### Updating Your Scripts on a Device
@@ -137,7 +138,7 @@ compiled Java files. So if your changes are Ruby-only, you can just run
     $ rake update_scripts
 
 to have it copy the current version of your scripts to your device.
-To update the scripts and restart the app in one go, run
+To update the scripts and restart the app in one go, run:
 
     $ rake update_scripts:restart
 
@@ -150,16 +151,16 @@ Caveats:
 This only works if your changes are all Ruby. If you have Java changes (which
 would generally just mean generating new classes) or changes to the xml, you
 will need to recompile your app.  The `update_scripts` task will revert to
-build the complete apk and install it if it detects non-Ruby source changes.
+build the complete .apk and install it if it detects non-Ruby source changes.
 
-On an actual device, you need to give the WRITE_EXTERNAL_STORAGE permission to
+On an actual device, you need to give the `WRITE_EXTERNAL_STORAGE` permission to
 your app, and scripts will be updated using the SDCARD on the device/emulator.
 
 Alternatively, you can also root your phone.
 
 ### Updating Ruboto's Files
 
-You can update various portions of your generated Ruboto app through the ruboto command:
+You can update various portions of your generated Ruboto app through the `ruboto` command:
 
 * JRuby:
 
@@ -180,24 +181,24 @@ Scripts
 -------
 
 The main thing Ruboto offers you is the ability to write Ruby scripts to define
-the behavior of Activities, BroadcastReceievers, and Services. (Eventually it'll
-be every class. It's setup such that adding in more classes should be trivial.)
+the behavior of Activities, BroadcastReceivers, and Services. (Eventually, it'll
+be every class. It's set up such that adding in more classes should be trivial.)
 
 Here's how it works:
 
 First of all, your scripts are found in the `src/` directory, and the script
 name is the same as the name of your class, only under_scored instead of
-CamelCased. Android classes have all of these methods that get called in certain
+CamelCased. Android classes have some standard methods that get called in certain
 situations. `Activity.onDestroy()` gets called when the activity gets killed,
-for example. Save weird cases (like the "launching" methods that need to setup
-JRuby), to script the method onFooBar, you call the Ruby method onFooBar on the
-Android object. That was really abstract, so here's an example.
+for example. Save weird cases (like the "launching" methods that are needed to set up
+JRuby), to call the method `onFooBar()`, you call the Ruby method `onFooBar` on the
+Android object. 
 
-You generate an app with the option `--activity FooActivity`, which means that
+That was really abstract, so here's an example. You generate an app with the option `--activity FooActivity`, which means that
 Ruboto will generate a FooActivity for you. So you open `src/foo_activity.rb` in
 your favorite text editor. If you want an activity that does nothing but Log
-when it gets launched and when it gets destroyed (in the onCreate and onPause
-methods). You want your script to look like this:
+when it gets launched and when it gets destroyed (in the `onCreate` and `onPause`
+methods,) you want your script to look like this:
 
 ```ruby
 class FooActivity
@@ -213,8 +214,8 @@ class FooActivity
 end
 ```
 
-The arguments passed to the methods are the same as the arguments that the java
-methods take. Consult the Android documentation.
+The arguments passed to the methods are the same as the arguments that the Java
+methods take. Consult the Android documentation for more information.
 
 Activities also have some special methods defined to make things easier. The
 easiest way to get an idea of what they are is looking over the
@@ -222,18 +223,18 @@ easiest way to get an idea of what they are is looking over the
 and the
 [tests](http://github.com/ruboto/ruboto/tree/master/test/activity/).
 You can also read the
-[ruboto source](http://github.com/ruboto/ruboto/blob/master/assets/src/ruboto)
+[Ruboto source](http://github.com/ruboto/ruboto/blob/master/assets/src/ruboto)
 where everything is defined.
 
 We also have many fine examples on the
-[WIKI](https://github.com/ruboto/ruboto/wiki).
+[Wiki](https://github.com/ruboto/ruboto/wiki).
 
 Testing
 -------
 
-For each generated class, a Ruby test script is created in the test/src
-directory.  For example if you generate a RubotoSampleAppActivity a file
-"test/src/ruboto_sample_app_activity_test.rb" file is created containing a
+For each generated class, a Ruby test script is created in the `test/src`
+directory.  For example, if you generate a RubotoSampleAppActivity, the file
+`test/src/ruboto_sample_app_activity_test.rb` is created containing a
 sample test script:
 
 ```ruby
@@ -260,7 +261,7 @@ test('button changes text') do |activity|
 end
 ```
 
-You run the tests for your app using ant or rake
+You can run the tests for your app using ant or rake:
 
     $ rake test
 
@@ -283,7 +284,7 @@ That's fine. Equally helpful:
 * When you gain enough wisdom, reconsider whether you could fork the project.
 
 If contributing code to the project, please run the existing tests and add tests
-for your changes.  You run the tests using rake
+for your changes.  You run the tests using rake:
 
     $ rake test
 
@@ -291,8 +292,8 @@ We have set up a matrix test that tests multiple configuations on the emulator:
 
     $ ./matrix_tests.sh
 
-All branches and pull requests on GitHub are also testd on
-https://travis-ci.org/ruboto/ruboto
+All branches and pull requests on GitHub are also tested on
+[https://travis-ci.org/ruboto/ruboto](https://travis-ci.org/ruboto/ruboto).
 
 Getting Help
 ------------
@@ -315,14 +316,14 @@ Tips & Tricks
 
 ### Emulators
 
-You can start an emulator corresponding to the api level of your project with
+You can start an emulator corresponding to the api level of your project with:
 
     $ ruboto emulator
 
-The emulator will be created for you and will be named after the android version
+The emulator will be created for you and will be named after the Android version
 of your project, like "Android_4.0.3".
 
-If you want to start an emulator for a specific API level use the "-t" option:
+If you want to start an emulator for a specific API level use the `-t` option:
 
     $ ruboto emulator -t 17
 
@@ -344,9 +345,9 @@ Alternatives
 If Ruboto's performance is a problem for you, check out
 [Mirah](http://mirah.org/) and [Garrett](http://github.com/technomancy/Garrett).
 
-Mirah is a language with Ruby-like syntax that compiles to java files. This
+Mirah is a language with Ruby-like syntax that compiles to Java files. This
 means that it adds no big runtime dependencies and has essentially the same
-performance as writing Java code because it essentially generates the same Java
+performance as writing Java code, as it essentially generates the same Java
 code that you would write. This makes it extremely well-suited for mobile
 devices where performance is a much bigger consideration.
 
@@ -360,8 +361,8 @@ Thanks go to:
 
 * Charles Nutter, a member of the JRuby core team, for mentoring this RSoC
   project and starting the Ruboto project in the first place with an
-  [irb](http://github.com/ruboto/ruboto-irb)
-* All of Ruby Summer of Code's [sponsors](http://rubysoc.org/sponsors)
+  [irb](http://github.com/ruboto/ruboto-irb).
+* All of Ruby Summer of Code's [sponsors](http://rubysoc.org/sponsors).
 * [Engine Yard](http://engineyard.com/) in particular for sponsoring RSoC and
   heavily sponsoring JRuby, which is obviously critical to the project.
 * All [contributors](http://github.com/ruboto/ruboto/contributors) and

data/RELEASE_CANDICATE_DOC

@@ -1,18 +1,16 @@
-Subject: [ANN] Ruboto 0.15.0 release candidate
+Subject: [ANN] Ruboto 0.16.0 release candidate
 
 Hi all!
 
-The Ruboto 0.15.0 release candidate is now available.
-
-In this release we stabilize the new SplashActivity feature and introduce
-a new rapid development cycle.
-
-Using "rake update_scripts:reload" changed Ruby scripts are pushed to the
-device/emulator and an intent is broadcasted to reload the files inside
-the running app, and the currently displayed activity is restarted.
-
-The process should take just a few seconds and avoids the full
-build->transfer->restart cycle.
+The Ruboto 0.16.0 release candidate is now available.
+
+In this release we add support for Android 4.4 KitKat!  You can also use
+git-based gems in your Gemfile.apk, and implement framework methods like
+onCreate in a Ruby Module and share them across Ruby classes.  We have
+expanded the Android Fragment support to allow the use of the Ruboto
+Widget DSL.  On the testing side, "ruboto setup" now downloads and
+installs HAXM which gives a 10 times speedup of the emulator!  For early
+adopters we now support Ruby 2.1 when using JRuby 9000 builds.
 
 As always we need your help and feedback to ensure the quality of the release.  Please install the release candidate using
 

data/RELEASE_DOC

@@ -1,6 +1,6 @@
-Subject: [ANN] Ruboto 0.15.0 released!
+Subject: [ANN] Ruboto 0.16.0 released!
 
-The Ruboto team is pleased to announce the release of Ruboto 0.15.0.
+The Ruboto team is pleased to announce the release of Ruboto 0.16.0.
 
 Ruboto (JRuby on Android) is a platform for developing full stand-alone
 apps for Android using the Ruby language and libraries.  It includes
@@ -8,52 +8,84 @@ support libraries and generators for creating projects, classes, tests,
 and more.  The complete APIs of Android, Java, and Ruby are available to
 you using the Ruby language.
 
-New in version 0.15.0:
-
-In this release we stabilize the new SplashActivity feature and introduce
-a new rapid development cycle.
-
-Using "rake update_scripts:reload" changed Ruby scripts are pushed to the
-device/emulator and an intent is broadcasted to reload the files inside
-the running app, and the currently displayed activity is restarted.
-
-The process should take just a few seconds and avoids the full
-build->transfer->restart cycle.
-
-Features:
-
-* Issue #12 Fast development with "rake update_scripts:reload"
-* Issue #461 Old API level files removed from repository as of 4.3
-* Issue #475 Reuse the original Intent when relaunching the user activity
-  after the SplashActivity has completed.
-* Issue #482 Better handling of "update_scripts" apk timestamp
-* Issue #486 Let "ruboto setup" download the latest version of a tool if
-  multiple versions exist.
-
+New in version 0.16.0:
+
+In this release we add support for Android 4.4 KitKat!  You can also use
+git-based gems in your Gemfile.apk, and implement framework methods like
+onCreate in a Ruby Module and share them across Ruby classes.  We have
+expanded the Android Fragment support to allow the use of the Ruboto
+Widget DSL.  On the testing side, "ruboto setup" now downloads and
+installs HAXM which gives a 10 times speedup of the emulator!  For early
+adopters we now support Ruby 2.1 when using JRuby 9000 builds.
+
+  Features:
+
+    * Issue #479 rake log
+* Issue #491 Add support for git-based gems
+* Issue #495 Send all script names to be reloaded in one intent to speed
+  up reload
+* Issue #497 Allow implementing framework methods like onCreate and
+  onResume in a Ruby module only.
+* Issue #498 Allow use of Ruboto Widget in fragments
+* Issue #499 Add shortcut "-t" for the "--target" option for "ruboto gen
+  app"
+* Issue #502 Use "ruboto emulator" to set up HAXM
+* Issue #503 Add "rake boing" as alias for "rake update_scripts:reload"
+* Issue #512 Ruby 2.1 support
+* Issue #517 Generate AVD with new format when running "ruboto emulator"
+* Issue #521 Add support for running emulator with Android 4.4 api level
+  19
+* Issue #526 Add KitKat (4.4) support
+    
 Bugfixes:
 
-* Issue #174 Ensure APK is not rebuilt if only Ruby source has changed
-* Issue #452 Android SDK command dx Not found
-* Issue #481 New Splash fails to start on Android 2.3
-* Issue #490 ruboto setup
-
+    * Issue #438 Updating android_api.xml breaks test ruboto_gen_test
+* Issue #448 Gems added from git repositories with the Gemfile.apk go
+  unrecognized.
+* Issue #484 "ruboto setup" doesn't work on mac
+* Issue #494 Ensure that the app is running before triggering reload of
+  scripts on device/emulator
+* Issue #496 require 'ruboto/activity' from 'ruboto/activity/reload' since
+  we depend on it.
+* Issue #504 Sporadically missing instance variable
+* Issue #509 Ruboto setup fails on windows with -y option
+* Issue #511 "ruboto update app" should rebuild JRubyAdapter.java based on
+  "ruboto.yml"
+* Issue #516 Spinner#adapter returns nil when used with the :adapter
+  option
+* Issue #519 Spinner should have prettier layout
+    
 Support:
 
-* Issue #469 Missing step in "Getting started": 1'. install GEMS
-
+    * Issue #522 rake BUILD FAILED - Windows and Linux
+    
+Documentation:
+
+    * Issue #492 Add tutorial for using fragments
+* Issue #493 README proofreading changes
+* Issue #508 Add AppSurfer as a sponsor.
+* Issue #514 Remove the 'ruboto update ruboto' command.  Use 'ruboto
+  update app' instead.
+* Issue #515 Add a "Contributors Wanted!" banner to the home page.
+* Issue #518 Sqlite_ar tutorial no longer works?
+    
 Pull requests:
 
-* Issue #474 Longer 'Timeout' time of BOSS process
-* Issue #477 Add readme.MD syntax highlight.
-
+    * Issue #458 Changed gem_paths to work with a gem pointing to repository
+  git in Gemfile.apk
+    
 Internal:
 
-* Issue #487 Start testing against JRuby 9000
-* Issue #488 Start testing against JRuby 1.7.5
+    * Issue #466 Need faster tests for Travis-CI
+    
+Other:
 
+    * Issue #478 rake debug problem on Windows
+* Issue #510 Ruboto setup on Windows fails to set path to dx
+    
 You can find a complete list of issues here:
 
-* https://github.com/ruboto/ruboto/issues?state=closed&milestone=29
+* https://github.com/ruboto/ruboto/issues?state=closed&milestone=30
 
 
 Installation:

data/Rakefile

@@ -1,4 +1,5 @@
 $:.unshift('lib') unless $:.include?('lib')
+require 'time'
 require 'date'
 require 'rake/clean'
 require 'rexml/document'
@@ -6,7 +7,10 @@ require 'ruboto/version'
 require 'ruboto/description'
 require 'ruboto/sdk_versions'
 require 'uri'
+require 'net/http'
 require 'net/https'
+require 'openssl'
+require 'yaml'
 
 PROJECT_DIR = File.expand_path(File.dirname(__FILE__))
 PLATFORM_PROJECT = File.expand_path('tmp/RubotoCore', File.dirname(__FILE__))
@@ -37,10 +41,12 @@ file GEM_FILE => GEM_SPEC_FILE do
 end
 
 task :install => :gem do
-  `RUBYOPT= gem query -i -n ^ruboto$ -v #{Ruboto::VERSION}`
+  old_rubyopt = ENV['RUBYOPT']
+  ENV['RUBYOPT'] = nil
+  `gem query -i -n ^ruboto$ -v #{Ruboto::VERSION}`
   if $? != 0
     puts 'Installing gem'
-    cmd = "RUBYOPT= gem install ruboto-#{Ruboto::VERSION}.gem"
+    cmd = "gem install ruboto-#{Ruboto::VERSION}.gem"
     output = `#{cmd}`
     if $? == 0
       puts output
@@ -50,13 +56,16 @@ task :install => :gem do
   else
     puts "ruboto-#{Ruboto::VERSION} is already installed."
   end
+  ENV['RUBYOPT'] = old_rubyopt
 end
 
 task :uninstall do
-  `RUBYOPT= gem query -i -n ^ruboto$ -v #{Ruboto::VERSION}`
+  old_rubyopt = ENV['RUBYOPT']
+  ENV['RUBYOPT'] = nil
+  `gem query -i -n ^ruboto$ -v #{Ruboto::VERSION}`
   if $? == 0
     puts 'Uninstalling gem'
-    cmd = "RUBYOPT= gem uninstall -x ruboto -v #{Ruboto::VERSION}"
+    cmd = "gem uninstall -x ruboto -v #{Ruboto::VERSION}"
     output = `#{cmd}`
     if $? == 0
       puts output
@@ -66,6 +75,7 @@ task :uninstall do
   else
     puts "ruboto-#{Ruboto::VERSION} is not installed."
   end
+  ENV['RUBYOPT'] = old_rubyopt
 end
 
 task :reinstall => [:uninstall, :clean, :install]
@@ -116,11 +126,6 @@ def get_github_issues
     print 'user name: '; user = STDIN.gets.chomp
     print ' password: '; pass = STDIN.gets.chomp
   end
-  require 'uri'
-  require 'net/http'
-  require 'net/https'
-  require 'openssl'
-  require 'yaml'
   host = 'api.github.com'
   base_uri = "https://#{host}/repos/ruboto/ruboto"
   https = Net::HTTP.new(host, 443)
@@ -132,7 +137,7 @@ def get_github_issues
   req.basic_auth(user, pass)
   res = https.start { |http| http.request(req) }
   milestones = YAML.load(res.body).sort_by { |i| Date.parse(i['due_on']) }
-  milestone_entry = milestones.find{|m| m['title'] == Ruboto::VERSION}
+  milestone_entry = milestones.find { |m| m['title'] == Ruboto::VERSION }
   raise "Milestone for version #{} not found." unless milestone_entry
   milestone = milestone_entry['number']
 
@@ -223,11 +228,11 @@ New in version #{milestone_name}:
 
 #{milestone_description}
 
-#{(categories.keys & grouped_issues.keys).map do |cat|
+  #{(categories.keys & grouped_issues.keys).map do |cat|
     "#{cat}:\n
-#{grouped_issues[cat].map { |i| %Q{* Issue ##{i['number']} #{i['title']}}.wrap(2) }.join("\n")}
-"
-end.join("\n")}
+    #{grouped_issues[cat].map { |i| %Q{* Issue ##{i['number']} #{i['title']}}.wrap(2) }.join("\n")}
+    "
+  end.join("\n")}
 You can find a complete list of issues here:
 
 * https://github.com/ruboto/ruboto/issues?state=closed&milestone=#{milestone}
@@ -302,14 +307,6 @@ end
 
 desc 'Fetch download stats form rubygems.org'
 task :stats do
-  require 'time'
-  require 'date'
-  require 'rubygems'
-  require 'uri'
-  require 'net/http'
-  require 'net/https'
-  require 'openssl'
-  require 'yaml'
   host = 'rubygems.org'
   base_uri = "https://#{host}/api/v1"
   https = Net::HTTP.new(host, 443)
@@ -397,7 +394,19 @@ task :test do
   ARGV.delete_if { |a| test_pattern.include? a }
   test_pattern.map! { |t| t[5..-1] }
   $: << File.expand_path('test', File.dirname(__FILE__))
-  (test_pattern.any? ? test_pattern : %w(test/*_test.rb)).map { |d| Dir[d] }.flatten.each do |f|
+  test_files = (test_pattern.any? ? test_pattern : %w(test/*_test.rb)).
+      map { |d| Dir[d] }.flatten.sort
+  if /(\d+)OF(\d+)/i =~ ENV['TEST_PART']
+    part_index = $1.to_i - 1
+    parts = $2.to_i
+    total_tests = test_files.size
+    files_in_part = total_tests.to_f / parts
+    start_index = (files_in_part * part_index).round
+    end_index = (files_in_part * (part_index + 1)).round - 1
+    test_files = test_files[start_index..end_index]
+    puts "Running tests #{start_index + 1}-#{end_index + 1} of #{total_tests}"
+  end
+  test_files.each do |f|
     require f.chomp('.rb')[5..-1]
   end
 end
@@ -571,8 +580,19 @@ end
 desc 'Download the latest jruby-jars snapshot'
 task :get_jruby_jars_snapshot do
   current_gem = 'jruby-jars-9000.dev.gem'
-  `wget http://ci.jruby.org/snapshots/master/#{current_gem}`
-  jars = Dir["#{current_gem}.*"]
-  jars[0..-2].each { |j| FileUtils.rm_f j } if jars.size > 1
-  FileUtils.mv(jars[-1], current_gem) if jars[-1]
+  print "Downloading #{current_gem}: \r"
+  uri = URI("http://ci.jruby.org/snapshots/master/#{current_gem}")
+  done = 0
+  body = ''
+  Net::HTTP.new(uri.host, uri.port).request_get(uri.path) do |response|
+    length = response['Content-Length'].to_i
+    response.read_body do |fragment|
+      body << fragment
+      done += fragment.length
+      progress = (done * 100) / length
+      print "Downloading #{current_gem}: #{done / 1024}/#{length / 1024}KB #{progress}%\r"
+    end
+    puts
+  end
+  File.open(current_gem, 'wb') { |f| f << body }
 end