juwelier 2.3.4 → 2.3.6

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: e6d90f41aec17c524cd9d16d1c6f3627ea4d7f3d
-  data.tar.gz: 815a192e1ae8a26497f3b26e53aca2b133f9687c
+  metadata.gz: da7ab0af1c0165d1bb78a81dcefdc5f9444d8963
+  data.tar.gz: ea8c2c9060d230921e2deff6edb7c9ab638a12e4
 SHA512:
-  metadata.gz: 6c04f047c6d324716b5af2db04b2e0f67bdbef182a01f812a675f5182fc2ca72225657d554511860673dc4b9d8f28a4b04182cf1db6e4c142134bfec42ce7ee2
-  data.tar.gz: 54230436efe962a82f9d24549e423786b00e1880bf9036b2a8df9288bef61089af0ccfe4d6043dbb8f726835bed884afa0eeda77e4385bc63bb9c1f02781f11a
+  metadata.gz: 41929dc46d991affc14ce5113910166747fa3d0269b804efe5dcc6949da4e4695f44fe67044bb644542350a706515f3ba50e711a3f6a2cf7960d22ae16fd6332
+  data.tar.gz: 3cbedef396c211f68e47e86fdc87610734ed3e4b0c592e845e2584aee53d33dc8b6c4fc664312e4b057140fb8ec3ea287fc1f79df6986efa120ad4e4aa730f79

data/.semver

@@ -1,5 +1,5 @@
 ---
 :major: 2
 :minor: 3
-:patch: 4
+:patch: 6
 :special: ''

data/.travis.yml

@@ -1,10 +1,9 @@
 language: ruby
+before_install:
+  - gem install bundler # need more up-to-date bundler to match Gemfile's
 rvm:
-  - 2.0.0
-  - 2.2.0
-  - 2.2.1
-  - 2.2.2
-  - 2.3.0
-  - 2.3.1
+  - 2.2.6
+  - 2.3.3
+  - 2.4.0
 notifications:
   irc: "irc.freenode.org#juwelier"

data/Gemfile

@@ -24,6 +24,7 @@ group :test do
   gem "shoulda"
   gem "mhennemeyer-output_catcher"
   gem "rr", ">= 1.0.4"
+  gem "test-unit-rr", "~> 1.0"
   gem "mocha"
   gem "redgreen"
   gem "test-construct"

data/README.markdown

@@ -10,6 +10,10 @@ maintaining both repos for a while, and eventually converge them to one. In
 the mean time, all new features shall be added to Juwelier, while keeping
 the origial Jeweler up-to-date with the latest Ruby releases.
 
+ALSO NOTE that I am transistioning the README to the orgmode format. As such,
+the Markdown version may be out of date, especially with the release notes
+and changelogs. Please refer to it instead.
+
 [![Build Status](https://travis-ci.org/flajann2/juwelier.png)](https://travis-ci.org/flajann2/juwelier)
 [![Coverage Status](https://coveralls.io/repos/flajann2/juwelier/badge.png)](https://coveralls.io/r/flajann2/juwelier)
 [![Dependency Status](https://www.versioneye.com/ruby/juwelier/2.0.0/badge.png)](https://www.versioneye.com/ruby/juwelier/2.0.0)
@@ -28,25 +32,27 @@ the origial Jeweler up-to-date with the latest Ruby releases.
  a migration option, but in the meantime, you may wish to
  run this bash script from the root directory of your project:
 
-    for f in $(grep -irl jeweler *)
-    do
-      sed -i 's/jeweler/juwelier/g' $f
-      sed -i 's/Jeweler/Juwelier/g' $f
-    done
-    bundle update
-    
+```bash
+for f in $(grep -irl jeweler *)
+do
+  sed -i 's/jeweler/juwelier/g' $f
+  sed -i 's/Jeweler/Juwelier/g' $f
+done
+bundle update
+```
+
  As you know, "Juwelier" is "Jeweler" in German. Since I
  have made Germany my new home, it only seemed approporiate.
- 
+
 ## Hello, world
 
 Use RubyGems to install the heck out of juwelier to get started:
 
-    $ gem install juwelier
+`$ gem install juwelier`
 
 With juwelier installed, you can use the `juwelier` command to generate a new project. For the most basic use, just give it a name:
 
-    $ juwelier hello-gem
+`$ juwelier hello-gem`
 
 This requires some Git configuration (like name, email, GitHub account, etc), but `juwelier` will prompt along the way.
 
@@ -70,40 +76,40 @@ Check out `juwelier --help` for the most up to date options.
 
 Beyond just editing source code, you'll be interacting with your gem using `rake` a lot. To see all the tasks available with a brief description, you can run:
 
-    $ rake -T
+`$ rake -T`
 
 You'll need a version before you can start installing your gem locally. The easiest way is with the `version:write` Rake task. Let's imagine you start with 0.1.0
 
-    $ rake version:write MAJOR=0 MINOR=1 PATCH=0
+`$ rake version:write MAJOR=0 MINOR=1 PATCH=0`
 
 You can now go forth and develop, now that there's an initial version defined. Eventually, you should install and test the gem:
 
-    $ rake install
+`$ rake install`
 
 The `install` rake task builds the gem and `gem install`s it. You're all set if you're using [RVM](http://rvm.beginrescueend.com/), but you may need to run it with sudo if you have a system-installed ruby:
 
-    $ sudo rake install
+`$ sudo rake install`
 
 ### Releasing
 
 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
+`$ rake release`
 
 This will automatically:
 
- *Juwelier Generate `hello-gem.gemspec` and commit it
+ * Juwelier Generate `hello-gem.gemspec` and commit it
  * 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
+`$ 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
+`$ 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
@@ -113,21 +119,23 @@ on `origin`) and release the gem.
 
 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:
 
-    # version:write like before
-    $ rake version:write MAJOR=0 MINOR=3 PATCH=0
+```bash
+# version:write like before
+$ rake version:write MAJOR=0 MINOR=3 PATCH=0
 
-    # bump just major, ie 0.1.0 -> 1.0.0
-    $ rake version:bump:major
+# bump just major, ie 0.1.0 -> 1.0.0
+$ rake version:bump:major
 
-    # bump just minor, ie 0.1.0 -> 0.2.0
-    $ rake version:bump:minor
+# bump just minor, ie 0.1.0 -> 0.2.0
+$ rake version:bump:minor
 
-    # bump just patch, ie 0.1.0 -> 0.1.1
-    $ rake version:bump:patch
+# bump just patch, ie 0.1.0 -> 0.1.1
+$ rake version:bump:patch
+```
 
 Then it's the same `release` we used before:
 
-    $ rake release
+`$ rake release`
 
 ## Customizing your gem
 
@@ -135,119 +143,119 @@ If you've been following along so far, your gem is just a blank slate. You're go
 
 You can customize your gem by updating your `Rakefile`. With a newly generated project, it will look something like this:
 
- Juwelier   require 'juwelier'
-    ::Tasks.new do |gem|
-      # 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}
-      gem.email = "fred.mitchell@gmx.com"
-      gem.homepage = "http://github.com/flajann2/whatwhatwhat"
-  Juwelier    gem.authors = ["Joshua Nichols"]
-    end
-  JuwelierJuwelier  ::RubygemsDotOrgTasks.new
+```ruby
+require 'juwelier'
+Juwelier::Tasks.new do |gem|
+  # 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}
+  gem.email = "fred.mitchell@gmx.com"
+  gem.homepage = "http://github.com/flajann2/whatwhatwhat"
+  gem.authors = ["Joshua Nichols"]
+end
+JuwelierJuwelier::RubygemsDotOrgTasks.new
+```
 
 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, -managed or not.  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://guides.rubygems.org/specification-reference/#name)
-
-    gem.summary = %Q{TODO: one-line summary of your gem}
-
-This is a one line summary of your gem. This is displayed, for example, when you use `gem list --details` or view it on [rubygems.org](http://rubygems.org/gems/).
-
-    gem.description = %Q{TODO: longer description of your gem}
+A short description about the configuration in the previous item.
 
-Description is a longer description. Scholars ascertain that knowledge of where the description is used was lost centuries ago.
+- **gem.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.email = "fred.mitchell@gmx.com"
+- **gem.summary**: This is a one line summary of your gem. This is displayed, for example, when you use `gem list --details` or view it on [rubygems.org](http://rubygems.org/gems/).
 
-This should be a way to get a hold of you regarding the gem.
+- **gem.description**: Description is a longer description. Scholars ascertain that knowledge of where the description is used was lost centuries ago.
 
-    gem.homepage = "http://github.com/flajann2/whatwhatwhat"
+- **gem.email**: This should be a way to get a hold of you regarding the gem.
 
-The homepage should have more information about your gem. The juwelier generator guesses this based on the assumption your code lives on [GitHub](http://github.com/), using your Git configuration to find your GitHub username. This is displayed by `gem list --details` and on rubygems.org.
+- **gem.homepage**: The homepage should have more information about your gem. The juwelier generator guesses this based on the assumption your code lives on [GitHub](http://github.com/), using your Git configuration to find your GitHub username. This is displayed by `gem list --details` and on rubygems.org.
 
-    gem.authors = ["Joshua Nichols"]
+- **gem.authors**: Hey, this is you, the author (or me in this case). The `juwelier` generator also guesses this from your Git configuration. This is displayed by `gem list --details` and on rubygems.org.
 
-Hey, this is you, the author (or me in this case). The `juwelier` generator also guesses this from your Git configuration. This is displayed by `gem list --details` and on rubygems.org.
+### Files
 
-##Juwelier# Files
+The quickest way to add more files is to `git add` them. Juwelier uses your git repository to populate your gem's files by including added and committed and excluding `.gitignore`d. In most cases, this is reasonable enough.
 
-ThJuweliere quickest way to add more files is to `git add` them.  uses your Git repository to populate your gem's files by including added and committed and excluding `.gitignore`d. In most cases, this is reasonable enough.
+If you need to tweak the files, that's cool. Juwelier populates `gem.files` as a `Rake::FileList`. It's like a normal array, except you can `include` and `exclude` file globs:
 
-If you need to tweak the files, that's cool.  populates `gem.files` as a `Rake::FileList`. It's like a normal array, except you can `include` and `exclude` file globs:
-
-    gem.files.exclude 'tmp' # exclude temporary directory
-    gem.files.include 'lib/foo/bar.rb' # explicitly include lib/foo/bar.rb
+```ruby
+gem.files.exclude 'tmp' # exclude temporary directory
+gem.files.include 'lib/foo/bar.rb' # explicitly include lib/foo/bar.rb
+```
 
 If that's not enough, you can just set `gem.files` outright
 
-    gem.files = Dir.glob('lib/**/*.rb')
+`gem.files = Dir.glob('lib/**/*.rb')`
 
 ### 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'
+`gem.add_dependency 'nokogiri'`
 
 This will ensure a version of `nokogiri` is installed, but it doesn't require anything more than that. You can provide extra args to be more specific:
 
-    gem.add_dependency 'nokogiri', '= 1.2.1' # exactly version 1.2.1
-    gem.add_dependency 'nokogiri', '>= 1.2.1' # greater than or equal to 1.2.1, ie, 1.2.1, 1.2.2, 1.3.0, 2.0.0, etc
-    gem.add_dependency 'nokogiri', '>= 1.2.1', '< 1.3.0' # greater than or equal to 1.2.1, but less than 1.3.0
-    gem.add_dependency 'nokogiri', '~> 1.2.1' # same thing, but more concise
+```ruby
+gem.add_dependency 'nokogiri', '= 1.2.1' # exactly version 1.2.1
+gem.add_dependency 'nokogiri', '>= 1.2.1' # greater than or equal to 1.2.1, ie, 1.2.1, 1.2.2, 1.3.0, 2.0.0, etc
+gem.add_dependency 'nokogiri', '>= 1.2.1', '< 1.3.0' # greater than or equal to 1.2.1, but less than 1.3.0
+gem.add_dependency 'nokogiri', '~> 1.2.1' # same thing, but more concise
+```
 
 When specifying which version is required, there's a bit of the condunrum. You want to allow the most versions possible, but you want to be sure they are compatible. Using `>= 1.2.1` is fine most of the time, except until the point that 2.0.0 comes out and totally breaks backwards the API. That's when it's good to use `~> 1.2.1`, which requires any version in the `1.2` family, starting with `1.2.1`.
 
-##Juwelier# Executables
+### Executables
 
 Executables let your gem install shell commands. Just put any executable scripts in the `bin/` directory, make sure they are added using `git`, and  will take care of the rest.
 
 When you need more finely grained control over it, you can set it yourself:
 
-    gem.executables = ['foo'] # note, it's the file name relative to `bin/`, not the project root
+`gem.executables = ['foo'] # note, it's the file name relative to bin/, not the project root`
 
 ### Versioning
 
-WeJuwelierJuwelier discussed earlier how to bump the version. The rake tasks are really just convience methods for manipulating the `VERSION` file. It just contains a version string, like `1.2.3`.
+We discussed earlier how to bump the version. The rake tasks are really just convience methods for manipulating the `VERSION` file. It just contains a version string, like `1.2.3`.
 
 `VERSION` is a convention used by , and is used to populate `gem.version`. You can actually set this yourself, and  won't try to override it:
 
-    gem.version = '1.2.3'
+`gem.version = '1.2.3'`
 
 A common pattern is to have this in a version constant in your library. This is convenient, because users of the library can query the version they are using at runtime.
 
-    # in lib/foo/version.rb
-    class Foo
-      module Version
-        MAJOR = 1
-        MINOR = 2
-        PATCH = 3
-        BUILD = 'pre3'
-
-        STRING = [MAJOR, MINOR, PATCH, BUILD].compact.join('.')
-      end
-    end
-
-    # in Rakefile
-  Juwelier  require 'juwelier'
-    require './lib/foo/version.rb'
-    ::Tasks.new do |gem|
-      # snip
-      gem.version = Foo::Version::STRING
-    end
-
-##Juwelier# Rake tasks
-
- lives inside of Rake. As a result, they are dear friends. But, that friendship doesn't interfere with typical Rake operations.
-
- The Juwelier Rake means you can define your own namespaces, tasks, or use third party Rake libraries without cause for concern.
-
-## Contributing to 
+```ruby
+# in lib/foo/version.rb
+class Foo
+  module Version
+    MAJOR = 1
+    MINOR = 2
+    PATCH = 3
+    BUILD = 'pre3'
+
+    STRING = [MAJOR, MINOR, PATCH, BUILD].compact.join('.')
+  end
+end
+```
+
+```ruby
+# in Rakefile
+require 'juwelier'
+require './lib/foo/version.rb'
+Juwelier::Tasks.new do |gem|
+  # snip
+  gem.version = Foo::Version::STRING
+end
+```
+
+### Rake tasks
+
+Juwelier tasks lives inside of Rake. As a result, they are dear friends. But, that friendship doesn't interfere with typical Rake operations.
+
+This means you can define your own namespaces, tasks, or use third party Rake libraries without cause for concern.
+
+## Contributing to
 
 * Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet
 * Ask on the [mailing list](http://groups.google.com/group/juwelier-rb) for feedback on your proposal, to see if somebody else has done it.

data/README.org

@@ -369,15 +369,17 @@ use third party Rake libraries without cause for concern.
 ** Release Notes
    | Version |       Date | Notes                                                                                                       |
    |---------+------------+-------------------------------------------------------------------------------------------------------------|
+   |   2.3.5 | 2017-02-10 | Revving Semver to be Semver2                                                                                |
    |   2.2.3 | 2016-11-21 | Psych bug fixed                                                                                             |
    |   2.2.2 | 2016-11-19 | Added support for pry -- includes pry, pry-byebug, pry-doc, pry-remote, pry-rescue. and pry-stack_explorer. |
    |   2.2.0 | 2016-11-19 | Bugs with --semver fixed, new options for using .org and .markdown for README                               |
    |   2.1.3 | 2016-11-19 | Problems with --semver, --required-version                                                                  |
 
 ** Known Issues
-   |       Date | Issue                                                                                          |
-   |------------+------------------------------------------------------------------------------------------------|
-   | 2016-11-19 | On generation of the Markdown, the initial title does not linefeed before the header sequence. |
+   |       Date | Issue                                                                                                    |
+   |------------+----------------------------------------------------------------------------------------------------------|
+   | 2017-02-10 | Orgmode and Markdown sync issue. They are out of sync for various reasons, and this must be ameorilated. |
+   | 2016-11-19 | On generation of the Markdown, the initial title does not linefeed before the header sequence.           |
 
 ** Contributing to
 

data/features/step_definitions/filesystem_steps.rb

@@ -21,7 +21,7 @@ Given /^I use the juwelier command to generate the "([^"]+)" project in the work
 end
 
 Given /^"([^"]+)" does not exist$/ do |file|
-  assert ! File.exists?(File.join(@working_dir, file))
+  assert ! File.exist?(File.join(@working_dir, file))
 end
 
 When /^I run "([^"]+)" in "([^"]+)"$/ do |command, directory|

data/features/step_definitions/generator_steps.rb

@@ -110,7 +110,7 @@ end
 Then /^a directory named '(.*)' is created$/ do |directory|
   directory = File.join(@working_dir, directory)
 
-  assert File.exists?(directory), "#{directory} did not exist"
+  assert File.exist?(directory), "#{directory} did not exist"
   assert File.directory?(directory), "#{directory} is not a directory"
 end
 
@@ -124,14 +124,14 @@ end
 Then /^a file named '(.*)' is created$/ do |file|
   file = File.join(@working_dir, file)
 
-  assert File.exists?(file), "#{file} expected to exist, but did not"
+  assert File.exist?(file), "#{file} expected to exist, but did not"
   assert File.file?(file), "#{file} expected to be a file, but is not"
 end
 
 Then /^a file named '(.*)' is not created$/ do |file|
   file = File.join(@working_dir, file)
 
-  assert ! File.exists?(file), "#{file} expected to not exist, but did"
+  assert ! File.exist?(file), "#{file} expected to not exist, but did"
 end
 
 Then /^a sane '.gitignore' is created$/ do

data/juwelier.gemspec

@@ -2,16 +2,16 @@
 # DO NOT EDIT THIS FILE DIRECTLY
 # Instead, edit Juwelier::Tasks in Rakefile, and run 'rake gemspec'
 # -*- encoding: utf-8 -*-
-# stub: juwelier 2.3.4 ruby lib
+# stub: juwelier 2.3.6 ruby lib
 
 Gem::Specification.new do |s|
   s.name = "juwelier".freeze
-  s.version = "2.3.4"
+  s.version = "2.3.6"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0".freeze) if s.respond_to? :required_rubygems_version=
   s.require_paths = ["lib".freeze]
   s.authors = ["Fred Mitchell".freeze, "Josh Nichols".freeze, "Yusuke Murata".freeze]
-  s.date = "2016-12-27"
+  s.date = "2017-04-24"
   s.description = "Simple and opinionated helper for creating Rubygem projects on GitHub".freeze
   s.email = ["fred.mitchell@gmx.de".freeze, "fred.mitchell@gmx.com".freeze, "info@muratayusuke.com".freeze]
   s.executables = ["juwelier".freeze]
@@ -194,7 +194,7 @@ Gem::Specification.new do |s|
   s.homepage = "http://github.com/flajann2/juwelier".freeze
   s.licenses = ["MIT".freeze]
   s.required_ruby_version = Gem::Requirement.new(">= 2.2.2".freeze)
-  s.rubygems_version = "2.6.8".freeze
+  s.rubygems_version = "2.6.11".freeze
   s.summary = "Powerful and Opinionated tool for creating and managing RubyGem projects".freeze
 
   if s.respond_to? :specification_version then

data/lib/juwelier.rb

@@ -159,7 +159,7 @@ class Juwelier
       base_dir = File.expand_path(self.base_dir || ".")
     end
     return nil if base_dir==File.dirname("/")
-    return base_dir if File.exists?(File.join(base_dir, '.git'))
+    return base_dir if File.exist?(File.join(base_dir, '.git'))
     return git_base_dir(base_dir)
   end    
 
@@ -168,7 +168,7 @@ class Juwelier
   end
 
   def version_file_exists?
-    File.exists?(@version_helper.plaintext_path) || File.exists?(@version_helper.yaml_path)
+    File.exist?(@version_helper.plaintext_path) || File.exist?(@version_helper.yaml_path)
   end
 
   def expects_version_file?

data/lib/juwelier/generator.rb

@@ -126,7 +126,7 @@ class Juwelier
         ["pry-rescue",         "~> 1"] <<
         ["pry-stack_explorer", "~> 0"] if should_use_pry
                                          
-      production_dependencies << ["semver", "~> 1.0.1"] if should_use_semver
+      production_dependencies << ["semver2", "~> 3"] if should_use_semver
 
       self.user_name       = options[:user_name]
       self.user_email      = options[:user_email]
@@ -201,7 +201,7 @@ class Juwelier
   private
 
     def create_files
-      unless File.exists?(target_dir) || File.directory?(target_dir)
+      unless File.exist?(target_dir) || File.directory?(target_dir)
         FileUtils.mkdir target_dir
       else
         raise FileInTheWay, "The directory #{target_dir} already exists, aborting. Maybe move it out of the way before continuing?"

data/lib/juwelier/version_helper.rb

@@ -39,7 +39,7 @@ class Juwelier
       end
 
       def read_yaml
-        if File.exists?(yaml_path)
+        if File.exist?(yaml_path)
           YAML.load_file(yaml_path)
         else
           raise VersionYmlError, "#{yaml_path} does not exist!"
@@ -86,12 +86,12 @@ class Juwelier
     def initialize(base_dir)
       self.base_dir = base_dir
 
-      if File.exists?(yaml_path)
+      if File.exist?(yaml_path)
         extend YamlExtension
         parse_yaml
       else
         extend PlaintextExtension
-        if File.exists?(plaintext_path)
+        if File.exist?(plaintext_path)
           parse_plaintext
         end
       end

data/test/juwelier/commands/test_release_to_git.rb

@@ -102,7 +102,7 @@ class Juwelier
           end
 
           should 'raise error' do
-            assert_raises RuntimeError, /try commiting/i do
+            assert_raises RuntimeError do
               @command.run
             end
           end
@@ -264,7 +264,7 @@ class Juwelier
           deleted { options[:deleted] }
           changed { options[:changed] }
         end
-        
+
       end
     end
   end

data/test/juwelier/commands/test_release_to_github.rb

@@ -120,7 +120,7 @@ class Juwelier
           end
 
           should 'raise error' do
-            assert_raises RuntimeError, /try commiting/i do
+            assert_raises RuntimeError do
               @command.run
             end
           end
@@ -470,7 +470,7 @@ class Juwelier
           deleted { options[:deleted] }
           changed { options[:changed] }
         end
-        
+
       end
     end
   end

data/test/juwelier/test_gemspec_helper.rb

@@ -30,7 +30,7 @@ class TestGemspecHelper < Test::Unit::TestCase
     end
 
     should "create gemspec file" do
-      assert File.exists?(@helper.path)
+      assert File.exist?(@helper.path)
     end
 
     should "make valid spec" do

data/test/juwelier/test_version_helper.rb

@@ -165,10 +165,10 @@ class TestVersionHelper < Test::Unit::TestCase
 
       should_have_version 0, 0, 1
       should "not create VERSION.yml" do
-        assert ! File.exists?(File.join(VERSION_TMP_DIR, 'VERSION.yml'))
+        assert ! File.exist?(File.join(VERSION_TMP_DIR, 'VERSION.yml'))
       end
       should "not create VERSION" do
-        assert ! File.exists?(File.join(VERSION_TMP_DIR, 'VERSION'))
+        assert ! File.exist?(File.join(VERSION_TMP_DIR, 'VERSION'))
       end
 
       context "outputting" do
@@ -177,7 +177,7 @@ class TestVersionHelper < Test::Unit::TestCase
         end
 
         should "create VERSION" do
-          assert File.exists?(File.join(VERSION_TMP_DIR, 'VERSION'))
+          assert File.exist?(File.join(VERSION_TMP_DIR, 'VERSION'))
         end
 
         context "re-reading VERSION" do

data/test/test_helper.rb

@@ -1,4 +1,6 @@
 require 'test/unit'
+require 'rr'
+require 'test/unit/rr'
 require 'rubygems'
 
 require 'bundler'
@@ -15,7 +17,6 @@ end
 
 require 'rake'
 require 'shoulda'
-require 'rr'
 #require 'redgreen'
 require 'construct'
 require 'git'
@@ -38,7 +39,6 @@ class RubyForgeStub
 end
 
 class Test::Unit::TestCase
-  include RR::Adapters::TestUnit unless include?(RR::Adapters::TestUnit)
   include Construct::Helpers
 
   def tmp_dir

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: juwelier
 version: !ruby/object:Gem::Version
-  version: 2.3.4
+  version: 2.3.6
 platform: ruby
 authors:
 - Fred Mitchell
@@ -10,7 +10,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2016-12-27 00:00:00.000000000 Z
+date: 2017-04-24 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rake
@@ -410,7 +410,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.6.8
+rubygems_version: 2.6.11
 signing_key: 
 specification_version: 4
 summary: Powerful and Opinionated tool for creating and managing RubyGem projects