jeweler 1.8.2 → 2.3.7

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 75a2defb36cb0375edbb24eb87a80772c4c0de3f
+  data.tar.gz: 58b9cda6bdbdadd2f71fb6f3c3ed74746bca294a
+SHA512:
+  metadata.gz: 9134a92692b58c7906c197f0e035bc22395491c62e2d30e53d47f161261a75ae8368dcc7f83844997f8207a8e44ae0064aaac7ebab1260b68861982f973268fa
+  data.tar.gz: edb76a82af7b5d81c2c6455ea96691b5d4fd5748ab8e341085de1692a368db335c98a656c05020b1ec754e15e5e54839ead6eae353b59f39093e75c5fd5e4b3b

data/.coveralls.yml

@@ -0,0 +1,2 @@
+service_name: travis-ci
+repo_token: AhkOkfc0MYCOqb24btF6YAac7cpKcm1Fw

data/.semver

@@ -0,0 +1,5 @@
+---
+:major: 2
+:minor: 3
+:patch: 7
+:special: ''

data/.travis.yml

@@ -1,7 +1,9 @@
 language: ruby
+before_install: 'gem update bundler'
+install: 'bundle install --jobs=3 --retry=3' # Suppress the --deployment flag'
 rvm:
-  - 1.8.7
-  - 1.9.2
-  - 1.9.3
+  - 2.2.2
+  - 2.3.0
+  - 2.3.1
 notifications:
   irc: "irc.freenode.org#jeweler"

data/ChangeLog.markdown

@@ -1,3 +1,33 @@
+# jeweler 2.2.1
+	* Added a patch for a potential psych problem that hit juwelier.
+				
+# jeweler 2.1.2, 2016-10-22
+  * Merged pull requests to support breaking changes to the Bundler API (thanks julik)
+  * Updated gem dependencies		
+				
+# jeweler 2.0.0, 2014-01-05
+
+ * Ruby 1.8 is not supported anymore.
+ * rake release accepts remote and branches #249
+
+# jeweler 1.8.7, 2013-08-12
+
+ * Lock timecop version to 0.6.1 to keep support of 1.8.7 #243
+ * Bump version in version.rb to reflect released gem version
+ * jeweler's Rakefile reads version from version.rb
+
+# jeweler 1.8.6, 2013-07-04
+
+ * Fix dependency error when install #239
+
+# jeweler 1.8.5, 2013-06-29
+
+ * Support rubygems 2.x #238
+
+# jeweler 1.8.2, 2012-01-24
+
+ * Fixed jeweler's circular dependency on itself #224
+
 # jeweler 1.8.2, 2012-01-24
 
  * Standardize on invoking jeweler in development: bundle exec jeweler #220

data/Gemfile

@@ -1,35 +1,42 @@
-source "http://rubygems.org"
-source "http://gems.github.com"
+source 'https://rubygems.org'
 
-# steal a page from bundler's gemspec:
-# add this directory as jeweler, in order to bundle exec jeweler and use the current working directory
-gem 'jeweler', :path => '.'
-
-gem "rake"
-gem "git", ">= 1.2.5"
-gem "bundler", "~> 1.0"
-gem "rdoc"
+gem 'rake'
+gem 'git', '>= 1.2.5'
+gem 'nokogiri', '>= 1.5.10'
+gem 'github_api', '~> 0.16.0'
+gem 'highline', '>= 1.6.15'
+gem 'bundler', '>= 1'
+gem 'rdoc'
+gem 'builder'
+gem "semver2"
+gem "psych", "~> 2.2"
 
 group :development do
-  gem "yard", "~> 0.7.4"
-  gem "rdoc"
-  gem "bluecloth"
-  gem "cucumber", "~> 1.1.4"
-  gem "rcov"
+  gem 'yard', '>= 0.8.5'
+  gem 'bluecloth'
+  gem 'cucumber', '>= 1.1.4'
+  gem 'simplecov'
 end
 
 group :test do
-  gem "timecop"
-  gem "activesupport", "~> 2.3.5"
-  gem "shoulda"
-  gem "mhennemeyer-output_catcher"
-  gem "rr", "~> 1.0.4"
-  gem "mocha"
-  gem "redgreen"
-  gem "test-construct"
-  gem "rake"
+  gem 'timecop'
+  gem 'activesupport', '~> 3.2.16'
+  gem 'shoulda', require: false
+  gem 'mhennemeyer-output_catcher'
+  gem 'mocha', require: false
+  gem 'redgreen'
+  gem 'test_construct'
+  gem 'coveralls', require: false
+  gem 'test-unit-rr', require: false
+end
+
+# yo dawg, i herd u lieked jeweler
+group :xzibit do
+  # steal a page from bundler's gemspec:
+  # add this directory as jeweler, in order to bundle exec jeweler and use the current working directory
+  gem 'jeweler', path: '.'
 end
 
 group :debug do
-  gem (RUBY_VERSION =~ /^1\.9/ ? "ruby-debug19" : "ruby-debug")
+  gem 'test-unit'
 end

data/Gemfile.lock

@@ -1,73 +1,144 @@
 PATH
   remote: .
   specs:
-    jeweler (1.8.1)
-      bundler (~> 1.0)
+    jeweler (2.3.7)
+      builder
+      bundler (>= 1)
       git (>= 1.2.5)
+      github_api (~> 0.16.0)
+      highline (>= 1.6.15)
+      nokogiri (>= 1.5.10)
+      psych (~> 2.2)
       rake
       rdoc
+      semver2
 
 GEM
-  remote: http://rubygems.org/
-  remote: http://gems.github.com/
+  remote: https://rubygems.org/
   specs:
-    activesupport (2.3.8)
-    bluecloth (2.0.7)
-    builder (3.0.0)
-    columnize (0.3.6)
-    cucumber (1.1.4)
+    activesupport (3.2.22.5)
+      i18n (~> 0.6, >= 0.6.4)
+      multi_json (~> 1.0)
+    addressable (2.4.0)
+    bluecloth (2.2.0)
+    builder (3.2.3)
+    coveralls (0.8.21)
+      json (>= 1.8, < 3)
+      simplecov (~> 0.14.1)
+      term-ansicolor (~> 1.3)
+      thor (~> 0.19.4)
+      tins (~> 1.6)
+    cucumber (2.4.0)
       builder (>= 2.1.2)
-      diff-lcs (>= 1.1.2)
-      gherkin (~> 2.7.1)
-      json (>= 1.4.6)
-      term-ansicolor (>= 1.0.6)
-    diff-lcs (1.1.3)
-    gherkin (2.7.4)
-      json (>= 1.4.6)
-    git (1.2.5)
-    json (1.6.3)
-    linecache (0.46)
-      rbx-require-relative (> 0.0.4)
+      cucumber-core (~> 1.5.0)
+      cucumber-wire (~> 0.0.1)
+      diff-lcs (>= 1.1.3)
+      gherkin (~> 4.0)
+      multi_json (>= 1.7.5, < 2.0)
+      multi_test (>= 0.1.2)
+    cucumber-core (1.5.0)
+      gherkin (~> 4.0)
+    cucumber-wire (0.0.1)
+    descendants_tracker (0.0.4)
+      thread_safe (~> 0.3, >= 0.3.1)
+    diff-lcs (1.3)
+    docile (1.1.5)
+    faraday (0.9.2)
+      multipart-post (>= 1.2, < 3)
+    gherkin (4.1.3)
+    git (1.3.0)
+    github_api (0.16.0)
+      addressable (~> 2.4.0)
+      descendants_tracker (~> 0.0.4)
+      faraday (~> 0.8, < 0.10)
+      hashie (>= 3.4)
+      mime-types (>= 1.16, < 3.0)
+      oauth2 (~> 1.0)
+    hashie (3.5.5)
+    highline (1.7.8)
+    i18n (0.8.4)
+    json (2.1.0)
+    jwt (1.5.6)
+    metaclass (0.0.4)
     mhennemeyer-output_catcher (1.0.1)
-    mocha (0.9.8)
-      rake
-    rake (0.9.2.2)
-    rbx-require-relative (0.0.5)
-    rcov (0.9.8)
-    rdoc (3.12)
-      json (~> 1.4)
+    mime-types (2.99.3)
+    mini_portile2 (2.2.0)
+    mocha (1.2.1)
+      metaclass (~> 0.0.1)
+    multi_json (1.12.1)
+    multi_test (0.1.2)
+    multi_xml (0.6.0)
+    multipart-post (2.0.0)
+    nokogiri (1.8.0)
+      mini_portile2 (~> 2.2.0)
+    oauth2 (1.4.0)
+      faraday (>= 0.8, < 0.13)
+      jwt (~> 1.0)
+      multi_json (~> 1.3)
+      multi_xml (~> 0.5)
+      rack (>= 1.2, < 3)
+    power_assert (1.0.2)
+    psych (2.2.4)
+    rack (2.0.3)
+    rake (12.0.0)
+    rdoc (5.1.0)
     redgreen (1.2.2)
-    rr (1.0.4)
-    ruby-debug (0.10.4)
-      columnize (>= 0.1)
-      ruby-debug-base (~> 0.10.4.0)
-    ruby-debug-base (0.10.4)
-      linecache (>= 0.3)
-    shoulda (2.11.3)
-    term-ansicolor (1.0.7)
-    test-construct (1.2.0)
-    timecop (0.3.5)
-    yard (0.7.4)
+    rr (1.2.0)
+    semver2 (3.4.2)
+    shoulda (3.5.0)
+      shoulda-context (~> 1.0, >= 1.0.1)
+      shoulda-matchers (>= 1.4.1, < 3.0)
+    shoulda-context (1.2.2)
+    shoulda-matchers (2.8.0)
+      activesupport (>= 3.0.0)
+    simplecov (0.14.1)
+      docile (~> 1.1.0)
+      json (>= 1.8, < 3)
+      simplecov-html (~> 0.10.0)
+    simplecov-html (0.10.1)
+    term-ansicolor (1.6.0)
+      tins (~> 1.0)
+    test-unit (3.2.4)
+      power_assert
+    test-unit-rr (1.0.5)
+      rr (>= 1.1.1)
+      test-unit (>= 2.5.2)
+    test_construct (2.0.1)
+    thor (0.19.4)
+    thread_safe (0.3.6)
+    timecop (0.9.0)
+    tins (1.14.0)
+    yard (0.9.9)
 
 PLATFORMS
   ruby
 
 DEPENDENCIES
-  activesupport (~> 2.3.5)
+  activesupport (~> 3.2.16)
   bluecloth
-  bundler (~> 1.0)
-  cucumber (~> 1.1.4)
+  builder
+  bundler (>= 1)
+  coveralls
+  cucumber (>= 1.1.4)
   git (>= 1.2.5)
+  github_api (~> 0.16.0)
+  highline (>= 1.6.15)
   jeweler!
   mhennemeyer-output_catcher
   mocha
+  nokogiri (>= 1.5.10)
+  psych (~> 2.2)
   rake
-  rcov
   rdoc
   redgreen
-  rr (~> 1.0.4)
-  ruby-debug
+  semver2
   shoulda
-  test-construct
+  simplecov
+  test-unit
+  test-unit-rr
+  test_construct
   timecop
-  yard (~> 0.7.4)
+  yard (>= 0.8.5)
+
+BUNDLED WITH
+   1.14.6

data/README.markdown

@@ -1,15 +1,27 @@
+*Jeweler maintenance has now shifted to Fred Mitchell*. I am now maintaining both Jeweler and its fork, juwelier. I will keep Jeweler at least functional with the latest Ruby releases, but put new features in Juwelier. Your input on this is more than welcome.
+
 # Jeweler: Craft the perfect RubyGem
 
+[![Join the chat at https://gitter.im/technicalpickles/jeweler](https://badges.gitter.im/technicalpickles/jeweler.svg)](https://gitter.im/technicalpickles/jeweler?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
+
 Jeweler provides the noble ruby developer with two primary features:
 
  * a library for managing and releasing RubyGem projects
  * a scaffold generator for starting new RubyGem projects
 
-[![Build Status](https://secure.travis-ci.org/technicalpickles/jeweler.png)](http://travis-ci.org/technicalpickles/jeweler])
+PLEASE NOTE that if you are starting afresh, please use the successor [Juwelier](https://github.com/flajann2/juwelier)
+I (Fred Mitchell, flajann2) will be maintaining both Jeweler and Juwelier, but will be adding new features to
+Juwelier, and eventually "merge" this one into Juwelier after some namespace issues
+are dealt with.
+
+[![Build Status](https://travis-ci.org/technicalpickles/jeweler.png)](https://travis-ci.org/technicalpickles/jeweler)
+[![Coverage Status](https://coveralls.io/repos/technicalpickles/jeweler/badge.png)](https://coveralls.io/r/technicalpickles/jeweler)
+[![Dependency Status](https://www.versioneye.com/ruby/jeweler/2.0.0/badge.png)](https://www.versioneye.com/ruby/jeweler/2.0.0)
+[![Code Climate](https://codeclimate.com/github/technicalpickles/jeweler/badges/gpa.svg)](https://codeclimate.com/github/technicalpickles/jeweler)
 
 ## Hello, world
 
-Use RubyGems to install the heck out of jeweler to get started: 
+Use RubyGems to install the heck out of jeweler to get started:
 
     $ gem install jeweler
 
@@ -55,7 +67,7 @@ The `install` rake task builds the gem and `gem install`s it. You're all set if
 
 ### Releasing
 
-At last, it's time to [ship it](http://img.skitch.com/20100310-nrgxbwqm58tibiq2un6mujqmm5.png)! Make sure you have everything committed and pushed, then go wild:
+At last, it's time to [ship it](http://shipitsquirrel.github.com/)! Make sure you have everything committed and pushed, then go wild:
 
     $ rake release
 
@@ -65,6 +77,19 @@ This will automatically:
  * Use `git` to tag `v0.1.0` and push it
  * Build `hello-gem-0.1.0.gem` and push it to [rubygems.org](http://rubygems.org/gems/)
 
+`rake release` accepts REMOTE(default: `origin`), LOCAL_BRANCH(default: `master`), REMOTE_BRANCH(default: `master`) and BRANCH(default: master)as options.
+
+    $ rake release REMOTE=upstream LOCAL_BRANCH=critical-security-fix REMOTE_BRANCH=v3
+
+This will tag and push the commits on your local branch named `critical-security-fix` to branch named `v3` in remote named `upstream` (if you have commit rights
+on `upstream`) and release the gem.
+
+    $ rake release BRANCH=v3
+
+If both remote and local branches are the same, use `BRANCH` option to simplify.
+This will tag and push the commits on your local branch named `v3` to branch named `v3` in remote named `origin` (if you have commit rights
+on `origin`) and release the gem.
+
 ### Version bumping
 
 It feels good to release code. Do it, do it often. But before that, bump the version. Then release it. There's a few ways to update the version:
@@ -93,7 +118,7 @@ You can customize your gem by updating your `Rakefile`. With a newly generated p
 
     require 'jeweler'
     Jeweler::Tasks.new do |gem|
-      # gem is a Gem::Specification... see http://docs.rubygems.org/read/chapter/20 for more options
+      # gem is a Gem::Specification... see http://guides.rubygems.org/specification-reference/ for more options
       gem.name = "whatwhatwhat"
       gem.summary = %Q{TODO: one-line summary of your gem}
       gem.description = %Q{TODO: longer description of your gem}
@@ -103,13 +128,13 @@ You can customize your gem by updating your `Rakefile`. With a newly generated p
     end
     Jeweler::RubygemsDotOrgTasks.new
 
-It's crucial to understand the `gem` object is just a Gem::Specification. You can read up about it at [docs.rubygems.org/read/chapter/20](http://docs.rubygems.org/read/chapter/20). This is the most basic way of specifying a gem, Jeweler-managed or not. Jeweler just exposes this to you, in addition to providing some reasonable defaults, which we'll explore now.
+It's crucial to understand the `gem` object is just a Gem::Specification. You can read up about it at [guides.rubygems.org/specification-reference](http://guides.rubygems.org/specification-reference/). This is the most basic way of specifying a gem, Jeweler-managed or not. Jeweler just exposes this to you, in addition to providing some reasonable defaults, which we'll explore now.
 
 ### Project information
 
     gem.name = "whatwhatwhat"
 
-Every gem has a name. Among other things, the gem name is how you are able to `gem install` it. [Reference](http://docs.rubygems.org/read/chapter/20#name)
+Every gem has a name. Among other things, the gem name is how you are able to `gem install` it. [Reference](http://guides.rubygems.org/specification-reference/#name)
 
     gem.summary = %Q{TODO: one-line summary of your gem}
 
@@ -146,7 +171,7 @@ If that's not enough, you can just set `gem.files` outright
 
 ### Dependencies
 
-Dependencies let you define other gems that your gem needs to function. `gem install your-gem` will install your-gem's dependencies along with it, and when you use your-gem in an application, the dependencies will be made available. Use `gem.add_dependency` to register them. [Reference](http://docs.rubygems.org/read/chapter/20#dependencies)
+Dependencies let you define other gems that your gem needs to function. `gem install your-gem` will install your-gem's dependencies along with it, and when you use your-gem in an application, the dependencies will be made available. Use `gem.add_dependency` to register them. [Reference](http://guides.rubygems.org/specification-reference/#add_development_dependency)
 
     gem.add_dependency 'nokogiri'
 
@@ -184,7 +209,7 @@ A common pattern is to have this in a version constant in your library. This is
         MINOR = 2
         PATCH = 3
         BUILD = 'pre3'
-    
+
         STRING = [MAJOR, MINOR, PATCH, BUILD].compact.join('.')
       end
     end
@@ -202,7 +227,7 @@ A common pattern is to have this in a version constant in your library. This is
 Jeweler lives inside of Rake. As a result, they are dear friends. But, that friendship doesn't interfere with typical Rake operations.
 
 That means you can define your own namespaces, tasks, or use third party Rake libraries without cause for concern.
-    
+
 ## Contributing to Jeweler
 
 * Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet
@@ -216,4 +241,5 @@ That means you can define your own namespaces, tasks, or use third party Rake li
 
 ## Copyright
 
-Copyright (c) 2008-2010 Josh Nichols. See LICENSE for details.
+Copyright (c) 2008-2010 Josh Nichols.
+Copyright (c) 2016 Fred Mitchell. See LICENSE for details.