retrospec 0.6.2 → 0.7.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: aac55e50a6a4eab445ab69d490d9110aba07356a
-  data.tar.gz: f822d911fcade21107729187bda937af362fc558
+  metadata.gz: 81a23cfd91f5fd7f280979484cfcd09f5706dcde
+  data.tar.gz: 76eea608c75ef1ee0fcd010823bd897ad1f00a87
 SHA512:
-  metadata.gz: ae5dea092c02ca028b6cff6ab15137758d3402e3c17fe4f41edd291c9b652027a820e206aa41c1d54c1b189e6ef18fddbdacd27f6cf3c1ef67b3f658ae138a3f
-  data.tar.gz: 17a7efd6c98c5f010ba48f31c76cb8575def80264967a321181170db4698f0b23745a6d3f58a83c6de2b69fe3f248cd7a6139d7994a3b21eb1169c10c15852b6
+  metadata.gz: 3607bea10d87afb8bb0c8d0efbe8d0cc6a1d0e19bb142c74687ac449933516cb12a6a2c7ba85229ffb368600fab260c4e85f4abee0978ab07fde03410045f28f
+  data.tar.gz: 31565e268795dcb6ae48b72e7a53990528c4778cf6a0cebba4396922c36d2371b1fd97e64c154b3b159a6c1aefdfdac68e57365f6705dab9338e3214af569a23

data/CHANGELOG.md

@@ -1,13 +1,29 @@
 # Retrospec Changelog
+
+## Unreleased
+
+## 0.7.0
+
+- Replace trollop with optimist (Fixes warning message)
+
 ## 0.6.2
- * Fixes a bug with safe_create_module_files not passing the filter
+
+- Fixes a bug with safe_create_module_files not passing the filter
+
 ## 0.6.1
- * Adds ability to create files from any template directory 
+
+- Adds ability to create files from any template directory
+
 ## 0.6.0
- * Adds the ability to filter out certain files from being generated
- * Adds the ability to sync any module file when it ends contains a .sync in the file name
+
+- Adds the ability to filter out certain files from being generated
+- Adds the ability to sync any module file when it ends contains a .sync in the file name
+
 ## 0.5.1
- * fixes gemspec spefication for runtime dependency
+
+- fixes gemspec spefication for runtime dependency
+
 ## 0.5.0
- * adds ability to overwrite files
- * removes jeweler dependency, and uses bundler tasks instead
+
+- adds ability to overwrite files
+- removes jeweler dependency, and uses bundler tasks instead

data/Gemfile

@@ -1,11 +1,11 @@
 source "http://rubygems.org"
-gem 'trollop'
+gem 'optimist', '~> 3.0.0'
 
 group :development do
   gem "rspec", "~> 3.2"
   gem "rdoc", "~> 3.12"
   gem 'rake'
-  gem "bundler", "~> 1.0"
+  gem "bundler", "~> 2.0"
   gem "simplecov", ">= 0"
   gem 'pry'
   gem "fakefs", :require => "fakefs/safe"

data/Gemfile.lock

@@ -1,66 +1,66 @@
 GEM
   remote: http://rubygems.org/
   specs:
-    ast (2.3.0)
-    coderay (1.1.0)
-    diff-lcs (1.2.5)
-    docile (1.1.5)
-    fakefs (0.6.7)
-    json (1.8.3)
-    method_source (0.8.2)
-    parser (2.3.3.1)
-      ast (~> 2.2)
-    powerpack (0.1.1)
-    pry (0.10.2)
+    ast (2.4.0)
+    coderay (1.1.2)
+    diff-lcs (1.3)
+    docile (1.3.2)
+    fakefs (0.20.1)
+    jaro_winkler (1.5.3)
+    json (1.8.6)
+    method_source (0.9.2)
+    optimist (3.0.0)
+    parallel (1.17.0)
+    parser (2.6.3.0)
+      ast (~> 2.4.0)
+    pry (0.12.2)
       coderay (~> 1.1.0)
-      method_source (~> 0.8.1)
-      slop (~> 3.4)
-    rainbow (2.2.1)
-    rake (10.4.2)
+      method_source (~> 0.9.0)
+    rainbow (3.0.0)
+    rake (12.3.2)
     rdoc (3.12.2)
       json (~> 1.4)
-    rspec (3.3.0)
-      rspec-core (~> 3.3.0)
-      rspec-expectations (~> 3.3.0)
-      rspec-mocks (~> 3.3.0)
-    rspec-core (3.3.2)
-      rspec-support (~> 3.3.0)
-    rspec-expectations (3.3.1)
+    rspec (3.8.0)
+      rspec-core (~> 3.8.0)
+      rspec-expectations (~> 3.8.0)
+      rspec-mocks (~> 3.8.0)
+    rspec-core (3.8.1)
+      rspec-support (~> 3.8.0)
+    rspec-expectations (3.8.4)
       diff-lcs (>= 1.2.0, < 2.0)
-      rspec-support (~> 3.3.0)
-    rspec-mocks (3.3.2)
+      rspec-support (~> 3.8.0)
+    rspec-mocks (3.8.1)
       diff-lcs (>= 1.2.0, < 2.0)
-      rspec-support (~> 3.3.0)
-    rspec-support (3.3.0)
-    rubocop (0.47.1)
-      parser (>= 2.3.3.1, < 3.0)
-      powerpack (~> 0.1)
-      rainbow (>= 1.99.1, < 3.0)
+      rspec-support (~> 3.8.0)
+    rspec-support (3.8.2)
+    rubocop (0.71.0)
+      jaro_winkler (~> 1.5.1)
+      parallel (~> 1.10)
+      parser (>= 2.6)
+      rainbow (>= 2.2.2, < 4.0)
       ruby-progressbar (~> 1.7)
-      unicode-display_width (~> 1.0, >= 1.0.1)
-    ruby-progressbar (1.8.1)
-    simplecov (0.10.0)
-      docile (~> 1.1.0)
-      json (~> 1.8)
+      unicode-display_width (>= 1.4.0, < 1.7)
+    ruby-progressbar (1.10.1)
+    simplecov (0.16.1)
+      docile (~> 1.1)
+      json (>= 1.8, < 3)
       simplecov-html (~> 0.10.0)
-    simplecov-html (0.10.0)
-    slop (3.6.0)
-    trollop (2.1.2)
-    unicode-display_width (1.1.3)
+    simplecov-html (0.10.2)
+    unicode-display_width (1.6.0)
 
 PLATFORMS
   ruby
 
 DEPENDENCIES
-  bundler (~> 1.0)
+  bundler (~> 2.0)
   fakefs
+  optimist (~> 3.0.0)
   pry
   rake
   rdoc (~> 3.12)
   rspec (~> 3.2)
   rubocop
   simplecov
-  trollop
 
 BUNDLED WITH
-   1.13.6
+   2.0.2

data/README.md

@@ -1,4 +1,5 @@
 # Retrospec
+
 [![Gem Version](https://badge.fury.io/rb/retrospec.svg)](http://badge.fury.io/rb/retrospec)
 [![Build Status](https://travis-ci.org/nwops/retrospec.png)](https://travis-ci.org/nwops/retrospec)
 
@@ -6,23 +7,24 @@ Retrospec is a framework that allows the automation of repetitive project file c
 project through the use of a pluggable architecture.
 
 The idea originally came from another project that performed the same function but was scoped to puppet module creation
-called [puppet-retrospec](https://github.com/nwops/puppet-retrospec.git).  The goal of puppet-retrospec was to document
+called [puppet-retrospec](https://github.com/nwops/puppet-retrospec.git). The goal of puppet-retrospec was to document
 the workflow and its best practices inside templates. This idea has now been generalized to cover any kind of project,
 therefore making it dead simple for anybody to get their project started with a simple command.
 
 There are two scenarios that this gem can be used for.
+
 1. Initial project creation
 2. Project augmentation
 
 The first scenario is to aid the creation of the project as many times information is spread across people, teams, blogs,
-forums and is often out of date.  By keeping this information in templates we have removed the burden of finding this
-information from the user.  However, there are many tools in existence today that already help in this area, but they
+forums and is often out of date. By keeping this information in templates we have removed the burden of finding this
+information from the user. However, there are many tools in existence today that already help in this area, but they
 are often not customizable.
 
-The second scenario it to augment an existing project that a user may have already started.  When this is the case
+The second scenario it to augment an existing project that a user may have already started. When this is the case
 retrospec can "retrofit" an existing project with the latest workflow and best practices based on the templates inside
-a plugin gem.  An existing project also contains information that can be used to automatically generate lots of files beyond just
-initial module creation.  A great example of this is with [puppet-retrospec](https://github.com/nwops/puppet-retrospec.git),
+a plugin gem. An existing project also contains information that can be used to automatically generate lots of files beyond just
+initial module creation. A great example of this is with [puppet-retrospec](https://github.com/nwops/puppet-retrospec.git),
 where the goal is to automaticly generate valid unit tests based on the code the author wrote. So as the user writes more
 code, they can easily create unit test files by just running retrospec.
 
@@ -41,25 +43,28 @@ This idea is inspried by a few projects:
 `gem install retrospec`
 
 ## Known issues
+
 If you have previously installed the puppet-retrospec gem, there is a conflict with the executable file `retrospec` because
-this gem also uses an executable file with the same name.  As a result I will be moving the legacy puppet-retrospec gem
-to a retrospec plugin that performs the same functionality.  But first I have to release this gem and the plugingem in order
+this gem also uses an executable file with the same name. As a result I will be moving the legacy puppet-retrospec gem
+to a retrospec plugin that performs the same functionality. But first I have to release this gem and the plugingem in order
 to move the puppet-retrospec to a plugin.
 
 ## Usage
 
 ### List Available Plugins
-By default the retrospec gem does not do anything but provide a framework for plugins.  In order to do anything you will
-need to install a retrospec plugin.  To see a list of plugins use: `retrospec -a` which will query the following [url](https://raw.githubusercontent.com/nwops/retrospec/master/available_plugins.yaml).
 
+By default the retrospec gem does not do anything but provide a framework for plugins. In order to do anything you will
+need to install a retrospec plugin. To see a list of plugins use: `retrospec -a` which will query the following [url](https://raw.githubusercontent.com/nwops/retrospec/master/available_plugins.yaml).
 
 ### Setting the module path
-Setting the module path is the only option that can change the outcome of the plugin.  By default it will use the current
+
+Setting the module path is the only option that can change the outcome of the plugin. By default it will use the current
 directory, but this can be overridden by using the `retrospec -m` option.
 
 ### Subcommands
-Subcommands are added dynamically to the help screen when installing new retrospec plugins. 
-So just use `retrospec -h` to see the list.  The name of the plugin is usually the name of subcommand. 
+
+Subcommands are added dynamically to the help screen when installing new retrospec plugins.
+So just use `retrospec -h` to see the list. The name of the plugin is usually the name of subcommand.
 
 ```
 retrospec -h
@@ -74,13 +79,14 @@ plugingen
   -h, --help                 Show this message
 ```
 
-Note: If you are really good at Trollop and can suggest a better way to display subcommands please let me know.  I was going
-for a git like interface but came up short. 
+Note: If you are really good at optimist and can suggest a better way to display subcommands please let me know. I was going
+for a git like interface but came up short.
 
 ### Using subcommands
+
 Once you find the subcommand you want just run the subcommand like: `retrospec -m tmp/test4 plugingen`. If you
-have already created your project you don't need to pass the `-m` option if your current working directory 
-is the root of your project.  So you may find yourself running `retrospec plugin_name` often inside your project.
+have already created your project you don't need to pass the `-m` option if your current working directory
+is the root of your project. So you may find yourself running `retrospec plugin_name` often inside your project.
 
 Getting help with a subcommand is easy as using `retrospec -m tmp/test4 plugin_name -h`
 
@@ -89,49 +95,51 @@ Getting help with a subcommand is easy as using `retrospec -m tmp/test4 plugin_n
 Options:
   -n, --name=<s>    The name of the new plugin (default: new_retrospec_plugin)
   -h, --help        Show this message
-```  
-
+```
 
 ### Retrspec config file
+
 Retrospec will read the config file at ~/.retrospec/config.yaml for configs related to retrospec itself or any plugins
-you install.  Since you may be running retrospec over and over it will be annoying to always have to specify this info
-so please refer to the plugin documentation for which options you can save to the config file.  At this time there are 
-no retrospec config options being read form the config file.  By default retrospec will add a simple config to ~/.retrospec
+you install. Since you may be running retrospec over and over it will be annoying to always have to specify this info
+so please refer to the plugin documentation for which options you can save to the config file. At this time there are
+no retrospec config options being read form the config file. By default retrospec will add a simple config to ~/.retrospec
 
 ## Plugins
-Please see the following [list](https://raw.githubusercontent.com/nwops/retrospec/master/available_plugins.yaml) for available plugins.
 
+Please see the following [list](https://raw.githubusercontent.com/nwops/retrospec/master/available_plugins.yaml) for available plugins.
 
 ## Plugin development and future plugin ideas
+
 Please see the [plugin document](plugin_development.md) for creating new retrospec plugins.
 
 Some ideas I have in my head for future plugins that should be created.
 
-* foreman plugin generator
-* foreman hammer cli plugin generator
-* smart-proxy plugin generator
-* nodejs project generator
-* chef module generator
-* ansible module generator
-* saltstack module generator  (possibly multiple types of plugins to create here)
-* groovy project generator
-* puppet module generator (in progress)
+- foreman plugin generator
+- foreman hammer cli plugin generator
+- smart-proxy plugin generator
+- nodejs project generator
+- chef module generator
+- ansible module generator
+- saltstack module generator (possibly multiple types of plugins to create here)
+- groovy project generator
+- puppet module generator (in progress)
 
-The sky is really the limit for what we can create since the usage is limited to any project that contains files. 
+The sky is really the limit for what we can create since the usage is limited to any project that contains files.
 
 ## Special file extensions
- * If a file contains `.sync` the file will be always be synced
- * If a file contains `.retrospec.erb` this tells retrospec that the file should be rendered as an erb file
- 
+
+- If a file contains `.sync` the file will be always be synced
+- If a file contains `.retrospec.erb` this tells retrospec that the file should be rendered as an erb file
+
 ## Contributing to retrospec
- 
-* Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet.
-* Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it.
-* Fork the project.
-* Start a feature/bugfix branch.
-* Commit and push until you are happy with your contribution.
-* Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
-* Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.
+
+- Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet.
+- Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it.
+- Fork the project.
+- Start a feature/bugfix branch.
+- Commit and push until you are happy with your contribution.
+- Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
+- Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.
 
 ## Copyright
 
@@ -139,5 +147,6 @@ Copyright (c) 2015 Corey Osman. See LICENSE.txt for
 further details.
 
 ## Paid Support
-Want to see new features developed much faster?  Contact me about a support contract so I can develop this tool during
-the day instead of after work.  contact: sales@logicminds.biz
+
+Want to see new features developed much faster? Contact me about a support contract so I can develop this tool during
+the day instead of after work. contact: sales@logicminds.biz

data/lib/retrospec/cli.rb

@@ -1,5 +1,5 @@
 require_relative 'plugins'
-require 'trollop'
+require 'optimist'
 require_relative '../retrospec'
 require_relative 'config'
 
@@ -13,7 +13,7 @@ module Retrospec
       sub_commands = cli.plugin_map.keys
       cmd_help = sub_commands.join("\n")
 
-      global_opts = Trollop::options do
+      global_opts = Optimist::options do
         version "#{Retrospec::VERSION} (c) Corey Osman"
         banner <<-EOS
 A framework to automate your development workflow by generating common files and test patterns.
@@ -52,7 +52,7 @@ Available subcommands:
           # this is the default action when no command is entered
           # at a later time we will try and use some magic to guess
           # what the user wants
-          Trollop.educate
+          Optimist.educate
         end
       end
     end

data/lib/retrospec/plugins/v1/plugin.rb

@@ -1,4 +1,4 @@
-require 'trollop'
+require 'optimist'
 require_relative 'module_helpers'
 require_relative 'context_object'
 

data/lib/retrospec/version.rb

@@ -1,4 +1,4 @@
 module Retrospec
-    VERSION = '0.6.2'
+    VERSION = '0.7.0'
 end
 

data/plugin_development.md

@@ -4,7 +4,8 @@ If you wish to automate the creation of a project or other project plugins you s
 create a retrospec plugin. Follow the steps below to create a plugin.
 
 ## Creating a plugin using the plugin generator
-1. Install the retrospec plugin that creates retrospec plugins!  `gem install retrospec-plugingen`
+
+1. Install the retrospec plugin that creates retrospec plugins! `gem install retrospec-plugingen`
 2. Come up with a name for you plugin.
 3. Use the retrospec plugin help `retrospec -m /path_to_project/plugin_name plugingen -h`
 4. Create the plugin `retrospec -m /path_to_project/plugin_name plugingen`
@@ -12,33 +13,38 @@ create a retrospec plugin. Follow the steps below to create a plugin.
 6. Hack --> Test --> Publish
 
 ## Choosing a plugin name
-By default the plugin generator will use the name of the directory or the name specified via the -n option.  This name
-will be used throughout the generator templates so its important to pick a sensible name.  The generator also uses the plugin_name
-as a class name although you are free to change it after creation. 
+
+By default the plugin generator will use the name of the directory or the name specified via the -n option. This name
+will be used throughout the generator templates so its important to pick a sensible name. The generator also uses the plugin_name
+as a class name although you are free to change it after creation.
 
 ### Naming the gem and repo
+
 Please ensure the gem name uses the following naming scheme retrospec-plugin_name and that your repo is also named retrospec-plugin_name.
-This will help everyone identify what the repo and gem do. 
+This will help everyone identify what the repo and gem do.
 
 Note: puppet-retrospec does not follow this standard due to a legacy name issue that would have caused confusion.
 
 ## What you need to override
-* self.run_cli
+
+- self.run_cli
 
 ## Create a context object
-By default the plugin generator will create a context object that can be used inside templates.  The default context object
+
+By default the plugin generator will create a context object that can be used inside templates. The default context object
 does not contain anything useful so you will want to customize this object only if your templates require variable interpolation.
 
 ## Main method to override
-Retrospec will call your plugin by running the plugin.run_cli class method.  You can do whatever you want in this method.
 
-The global_opts are the options passed into the retrospec command which are specific to retrospec.  Additionally, the 
-global_config  (~/.retrospec/config.yaml) is a hash map of the entire config while the plugin_config is a subset that pertains
+Retrospec will call your plugin by running the plugin.run_cli class method. You can do whatever you want in this method.
+
+The global_opts are the options passed into the retrospec command which are specific to retrospec. Additionally, the
+global_config (~/.retrospec/config.yaml) is a hash map of the entire config while the plugin_config is a subset that pertains
 only to your plugin.
 
-In this method you should at least call self.new() on your plugin and then plugin_instance.run.  
+In this method you should at least call self.new() on your plugin and then plugin_instance.run.
 
-For simplicity sake you can also just copy and paste this into your method.  This is the default layout when using 
+For simplicity sake you can also just copy and paste this into your method. This is the default layout when using
 the retrospec plugin generator.
 
 ```ruby
@@ -50,7 +56,7 @@ def self.run_cli(global_opts, global_config, plugin_config)
     else
       sub_command_help = ""
     end
-    plugin_opts = Trollop::options do
+    plugin_opts = optimist::options do
       version "#{Retrospec::Pluginname::VERSION} (c) Your Name"
       banner <<-EOS
 Some description goes here.\n
@@ -77,11 +83,10 @@ Some description goes here.\n
 end
 ```
 
-See the [trollop documentation](http://trollop.rubyforge.org) for more info.
+See the [optimist documentation](http://optimist.rubyforge.org) for more info.
 
 ## Module helpers
+
 The module helpers module is included by default and contains useful methods to safely create files. When creating files
 use the safe create methods in order to protect the users content from being overwritten.  
 For a list of methods please see the [source code](https://github.com/nwops/retrospec/blob/master/lib/retrospec/plugins/v1/module_helpers.rb)
-
-

data/retrospec.gemspec

@@ -35,7 +35,7 @@ Gem::Specification.new do |spec|
   spec.bindir        = 'bin'
   spec.executables   = spec.files.grep(%r{^bin/}) { |f| File.basename(f) }
   spec.require_paths = ['lib']
-  spec.add_runtime_dependency 'trollop'
+  spec.add_runtime_dependency(%q<optimist>, ["~> 3.0.0"])
   spec.add_development_dependency 'bundler', '~> 1.13'
   spec.add_development_dependency 'rake', '~> 10.0'
   spec.add_development_dependency 'rspec', '~> 3.0'

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: retrospec
 version: !ruby/object:Gem::Version
-  version: 0.6.2
+  version: 0.7.0
 platform: ruby
 authors:
 - Corey Osman
@@ -11,115 +11,115 @@ cert_chain: []
 date: 2017-04-17 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
-  name: trollop
+  name: optimist
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: '0'
+        version: 3.0.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: '0'
+        version: 3.0.0
 - !ruby/object:Gem::Dependency
   name: bundler
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ~>
+    - - "~>"
       - !ruby/object:Gem::Version
         version: '1.13'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ~>
+    - - "~>"
       - !ruby/object:Gem::Version
         version: '1.13'
 - !ruby/object:Gem::Dependency
   name: rake
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ~>
+    - - "~>"
       - !ruby/object:Gem::Version
         version: '10.0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ~>
+    - - "~>"
       - !ruby/object:Gem::Version
         version: '10.0'
 - !ruby/object:Gem::Dependency
   name: rspec
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ~>
+    - - "~>"
       - !ruby/object:Gem::Version
         version: '3.0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ~>
+    - - "~>"
       - !ruby/object:Gem::Version
         version: '3.0'
 - !ruby/object:Gem::Dependency
   name: pry
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
   name: simplecov
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
   name: fakefs
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
   name: rubocop
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '0'
 description: Retrospec is a framework that allows the automation of repetitive file
@@ -133,10 +133,10 @@ extra_rdoc_files:
 - LICENSE.txt
 - README.md
 files:
-- .document
-- .gitignore
-- .rspec
-- .travis.yml
+- ".document"
+- ".gitignore"
+- ".rspec"
+- ".travis.yml"
 - CHANGELOG.md
 - Gemfile
 - Gemfile.lock
@@ -169,17 +169,17 @@ require_paths:
 - lib
 required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
-  - - '>='
+  - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - '>='
+  - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.0.14.1
+rubygems_version: 2.5.2.3
 signing_key: 
 specification_version: 4
 summary: A devops framework for automating your development workflow