From b878e762c0705a5fd109c686328b1508595876e0 Mon Sep 17 00:00:00 2001
From: David Maloney <DMaloney@rapid7.com>
Date: Thu, 10 Mar 2016 15:39:06 -0600
Subject: [PATCH] pin rake version to 1.x line

rake 11 remvoes the last_comment method which
causes a error when trying to run rake jobs
current guidance is to pin the version back to
before the change

MS-1230
---
 Gemfile      | 2 +-
 Gemfile.lock | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/Gemfile b/Gemfile
index efced5ce12..d7ac7c4cbf 100755
--- a/Gemfile
+++ b/Gemfile
@@ -36,7 +36,7 @@ group :development, :test do
   # Make rspec output shorter and more useful
   gem 'fivemat', '~> 1.3.1'
   # running documentation generation tasks and rspec tasks
-  gem 'rake', '>= 10.0.0'
+  gem 'rake', '~> 10.5'
   # Define `rake spec`.  Must be in development AND test so that its available by default as a rake test when the
   # environment is development
   gem 'rspec-rails' , '~> 3.3'
diff --git a/Gemfile.lock b/Gemfile.lock
index e2e287d4d0..8dc7a49ea3 100644
--- a/Gemfile.lock
+++ b/Gemfile.lock
@@ -237,7 +237,7 @@ GEM
       activesupport (= 4.1.15)
       rake (>= 0.8.7)
       thor (>= 0.18.1, < 2.0)
-    rake (11.0.1)
+    rake (10.5.0)
     rb-readline-r7 (0.5.2.0)
     recog (2.0.14)
       nokogiri
@@ -305,7 +305,7 @@ DEPENDENCIES
   metasploit-yard!
   metasploit_data_models!
   pry
-  rake (>= 10.0.0)
+  rake (~> 10.5)
   redcarpet
   rspec-rails (~> 3.3)
   shoulda-matchers