rake 10.3.1 → 10.3.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 7fb874143d83d469b8c5f9e4fc8ff79f736a89ef
-  data.tar.gz: 0a9bf5d92a94e2183b7887415732521b293c5750
+  metadata.gz: 0caac57ec31c4e81580a89a857cea98ade615eef
+  data.tar.gz: e505354568b86ee4850b446e7f938dd8ea3872e1
 SHA512:
-  metadata.gz: fde0747e99905b6fb93b4d9fd788cdcf6e751966a9b7cf10ddefcfd109e78dff5d87841194c81cd8cd4b9f069f61386e845130ee338b157ddf378936c40a3326
-  data.tar.gz: 632c9e14454097041663c31d2aa689114c9335add9efe4965d3aad67694247af90c194613ab3f8a07197b171aa96b2a0781e6d282de59c87653067797e2ca951
+  metadata.gz: 86d3dc72939bd00ad29b791495cbbab200b4ba996237d2644384d7fa10c8dd9c761389eee573ff6767996266818cb0bb4f39096ad043610dea017cc0f9c1435e
+  data.tar.gz: 0d54d81c43e9d6de2c5d685bebde241f22d5c0e87d0dc45f7dd725bf61a95e86cfca9903195aba4a8a8617c53d50c09d9a56a0c1f44e34e0ee5b7df6ebde0895

checksums.yaml.gz.sig

@@ -1,3 +1,2 @@
-1�K��O=gh�4zC뤞���ܪ�.
:�?���
-b��Ž��.�ʵ�$�=ZQ�{;�To�����5���}��wLؚ��������jLE�&�=�V9�Q,�
-K���;fGW
+W]�s�4Y�3
+T�*=��S�A;$�k
+^����Qޯ������4�����]Eg��m���{�X�������"-�o_9#���Cp/p|�xv���'��B�kC�/���l,�J�p2%ۧ0��`0�
�����ըX����:�a��_1c�Y��h�&�t+�yO�Z�����}ʙ��3LS!O�7�Z���ln/��"�)��ё����DUfN�t�5�$P�4F���ɣ������<�����������7Qe����Z�A�O

data/CONTRIBUTING.rdoc

@@ -0,0 +1,34 @@
+= Source Repository
+
+Rake is currently hosted at github. The github web page is
+http://github.com/jimweirich/rake . The public git clone URL is
+
+  git://github.com/jimweirich/rake.git
+
+= Running the Rake Test Suite
+
+If you wish to run the unit and functional tests that come with Rake:
+
+* CD into the top project directory of rake.
+* Type one of the following:
+
+    rake newb    # If you have never run rake's tests
+    rake         # If you have run rake's tests
+
+= Issues and Bug Reports
+
+Feel free to submit commits or feature requests.  If you send a patch,
+remember to update the corresponding unit tests.  In fact, I prefer
+new feature to be submitted in the form of new unit tests.
+
+For other information, feel free to ask on the ruby-talk mailing list.
+
+If you have found a bug in rake please try with the latest version of rake
+before filing an issue.  Also check History.rdoc for bug fixes that may have
+addressed your issue.
+
+When submitting pull requests please check the rake Travis-CI page for test
+failures:
+
+  https://travis-ci.org/jimweirich/rake
+

data/History.rdoc

@@ -1,3 +1,11 @@
+=== 10.3.2 / 2014-05-15
+
+Bug fixes:
+
+* Rake no longer infinitely loops when showing exception causes that refer to
+  each other.  Bug #272 by Chris Bandy.
+* Fixed documentation typos.  Bug #275 by Jake Worth.
+
 === 10.3.1 / 2014-04-17
 
 Bug fixes:

data/MIT-LICENSE

@@ -1,4 +1,4 @@
-Copyright (c) 2003, 2004 Jim Weirich
+Copyright (c) Jim Weirich
 
 Permission is hereby granted, free of charge, to any person obtaining
 a copy of this software and associated documentation files (the

data/Manifest.txt

@@ -1,6 +1,7 @@
 .autotest
 .rubocop.yml
 .togglerc
+CONTRIBUTING.rdoc
 History.rdoc
 MIT-LICENSE
 Manifest.txt

data/README.rdoc

@@ -2,6 +2,7 @@
 
 home :: https://github.com/jimweirich/rake
 bugs :: https://github.com/jimweirich/rake/issues
+docs :: http://docs.seattlerb.org/rake
 
 == Description
 
@@ -34,7 +35,7 @@ Rake has the following features:
 
 Download and install rake with the following.
 
-   gem install rake
+  gem install rake
 
 == Usage
 
@@ -43,7 +44,7 @@ Download and install rake with the following.
 First, you must write a "Rakefile" file which contains the build rules. Here's
 a simple example:
 
-  task :default => [:test]
+  task default: %w[test]
 
   task :test do
     ruby "test/unittest.rb"
@@ -51,8 +52,8 @@ a simple example:
 
 This Rakefile has two tasks:
 
-* A task named "test", which - upon invocation - will run a unit test file in
-  Ruby.
+* A task named "test", which -- upon invocation -- will run a unit test file
+  in Ruby.
 * A task named "default". This task does nothing by itself, but it has exactly
   one dependency, namely the "test" task. Invoking the "default" task will
   cause Rake to invoke the "test" task as well.
@@ -69,64 +70,27 @@ Running the "rake" command without any options will cause it to run the
 
 Type "rake --help" for all available options.
 
+== Resources
 
-=== More Information
+=== Rake Information
 
-* For details on Rake's command-line invocation, read
-  doc/command_line_usage.rdoc[https://github.com/jimweirich/rake/blob/master/doc/command_line_usage.rdoc]
-* For details on writing Rakefiles, see
-  doc/rakefile.rdoc[https://github.com/jimweirich/rake/blob/master/doc/rakefile.rdoc].
-* For the original announcement of Rake, see
-  doc/rational.rdoc[https://github.com/jimweirich/rake/blob/master/doc/rational.rdoc].
-* For a glossary of terms, see
-  doc/glossary.rdoc[https://github.com/jimweirich/rake/blob/master/doc/glossary.rdoc].
-
-== Development
-
-=== Source Repository
-
-Rake is currently hosted at github. The github web page is
-http://github.com/jimweirich/rake . The public git clone URL is
-
-* git://github.com/jimweirich/rake.git
-
-=== Running the Rake Test Suite
-
-If you wish to run the unit and functional tests that come with Rake:
-
-* Install the 'flexmock' gem
-* Install the 'session' gem in order to run the functional tests.
-* CD into the top project directory of rake.
-* Type one of the following:
-
-     rake                  # If you have a version of rake installed
-     ruby -Ilib bin/rake   # If you do not have a version of rake installed.
-
-=== Issues and Bug Reports
-
-Feature requests and bug reports can be made here
-
-* https://github.com/jimweirich/rake/issues
-
-== Online Resources
-
-=== Rake References
-
-* Rake Documentation Home: http://docs.rubyrake.org
-* Rake Project Page: http://github.com/jimweirich/rake
-* Rake API Documents: http://onestepback.org/software/rake/
-* Rake Source Code Repo:  http://github.com/jimweirich/rake
-* Rake Git Repo Clone URL: git://github.com/jimweirich/rake.git
-* Rake Bug Reports: https://github.com/jimweirich/rake/issues
-* Rake Continuous Build Server: https://travis-ci.org/#!/jimweirich/rake
+* {Rake command-line}[rdoc-ref:doc/command_line_usage.rdoc]
+* {Writing Rakefiles}[rdoc-ref:doc/rakefile.rdoc]
+* The original {Rake announcement}[rdoc-ref:doc/rational.rdoc]
+* Rake {glossary}[rdoc-ref:doc/glossary.rdoc]
 
 === Presentations and Articles about Rake
 
+* Avdi Grimm's rake series:
+  1. {Rake Basics}[http://devblog.avdi.org/2014/04/21/rake-part-1-basics/]
+  2. {Rake File Lists}[http://devblog.avdi.org/2014/04/22/rake-part-2-file-lists/]
+  3. {Rake Rules}[http://devblog.avdi.org/2014/04/23/rake-part-3-rules/]
+  4. {Rake Pathmap}[http://devblog.avdi.org/2014/04/24/rake-part-4-pathmap/]
 * Jim Weirich's 2003 RubyConf presentation:
   http://onestepback.org/articles/buildingwithrake/
 * Martin Fowler's article on Rake: http://martinfowler.com/articles/rake.html
 
-== Other Make Reinvisionings ...
+== Other Make Re-envisionings ...
 
 Rake is a late entry in the make replacement field.  Here are links to
 other projects with similar (and not so similar) goals.
@@ -155,32 +119,19 @@ Rake is available under an MIT-style license.
 
 :include: MIT-LICENSE
 
-== Support
-
-The Rake homepage is http://onestepback.org/software/rake/.  You can find the Rake
-GitHub page at http://github.com/jimweirich/rake.
-
-Feel free to submit commits or feature requests.  If you send a patch,
-remember to update the corresponding unit tests.  In fact, I prefer
-new feature to be submitted in the form of new unit tests.
-
-For other information, feel free to ask on the ruby-talk mailing list
-(which is mirrored to comp.lang.ruby) or contact
-jim dot weirich at gmail.com.
-
 ---
 
 = Other stuff
 
 Author::   Jim Weirich <jim.weirich@gmail.com>
-Requires:: Ruby 1.9 or later
-License::  Copyright 2003-2013 by Jim Weirich.
+Requires:: Ruby 1.8.7 or later
+License::  Copyright Jim Weirich.
            Released under an MIT-style license.  See the MIT-LICENSE
            file included in the distribution.
 
 == Warranty
 
-This software is provided "as is" and without any express or
-implied warranties, including, without limitation, the implied
-warranties of merchantibility and fitness for a particular
-purpose.
+This software is provided "as is" and without any express or implied
+warranties, including, without limitation, the implied warranties of
+merchantability and fitness for a particular purpose.
+

data/doc/command_line_usage.rdoc

@@ -20,7 +20,7 @@ Options are:
     tracing details). The _output_ parameter is optional, but if
     specified it controls where the backtrace output is sent. If
     _output_ is <tt>stdout</tt>, then backtrace output is directed to
-    stardard output. If _output_ is <tt>stderr</tt>, or if it is
+    standard output. If _output_ is <tt>stderr</tt>, or if it is
     missing, then the backtrace output is sent to standard error.
 
 [<tt>--comments</tt>]
@@ -49,7 +49,7 @@ Options are:
 
 [<tt>--jobs</tt> _number_  (-j)]
 
-    Specifies the maximun number of concurrent threads allowed. Rake
+    Specifies the maximum number of concurrent threads allowed. Rake
     will allocate threads as needed up to this maximum number.
 
     If omitted, Rake will attempt to estimate the number of CPUs on
@@ -135,7 +135,7 @@ Options are:
     Turn on invoke/execute tracing. Also enable full backtrace on
     errors. The _output_ parameter is optional, but if specified it
     controls where the trace output is sent. If _output_ is
-    <tt>stdout</tt>, then trace output is directed to stardard output.
+    <tt>stdout</tt>, then trace output is directed to standard output.
     If _output_ is <tt>stderr</tt>, or if it is missing, then trace
     output is sent to standard error.
 

data/doc/glossary.rdoc

@@ -1,51 +1,43 @@
 = Glossary
 
-[<b>action</b>]
-	Code to be executed in order to perform a task.  Actions in a
-	rakefile are specified in a code block (usually delimited by
-	+do+/+end+ pairs.
-
-[<b>execute</b>]
-	When a task is executed, all of its actions are performed, in
-	the order they were defined.  Note that unlike
-	<tt>invoke</tt>, <tt>execute</tt> always executes the actions
-	(without invoking or executing the prerequisites).
-
-[<b>file task</b> (FileTask)]
-	 A file task is a task whose purpose is to create a file
-	 (which has the same name as the task).  When invoked, a file
-	 task will only execute if one or more of the following
-	 conditions are true.
-
-         1. The associated file does not exist.
-	 2. A prerequisite has a later time stamp than the existing file.
-
-	 Because normal Tasks always have the current time as
-	 timestamp, a FileTask that has a normal Task prerequisite
-	 will always execute.
-
-[<b>invoke</b>]
-	When a task is invoked, first we check to see if it has been
-	invoked before.  if it has been, then nothing else is done.
-	If this is the first time its been invoked, then we invoke
-	each of its prerequisites.  Finally, we check to see if we
-	need to execute the actions of this task by calling
-	<tt>needed?</tt>.  Finally, if the task is needed, we execute
-	its actions.
-
-	NOTE: Currently prerequisites are invoked even if the task is
-	not needed.  This may change in the future.
-
-[<b>prerequisites</b>]
-	Every task has a set (possibly empty) of prerequisites.  A
-	prerequisite P to Task T is itself a task that must be invoked
-	before Task T.
-
-[<b>rule</b>]
-	A rule is a recipe for synthesizing a task when no task is
-	explicitly defined.  Rules generally synthesize file tasks.
-
-[<b>task</b> (Task)]
-	Basic unit of work in a rakefile.  A task has a name, a set of
-	prerequisites and a list of actions to be performed.
+action ::
+  Code to be executed in order to perform a task.  Actions in a rakefile are
+  specified in a code block (usually delimited by +do+/+end+ pairs.
+
+execute ::
+  When a task is executed, all of its actions are performed, in the order they
+  were defined.  Note that unlike <tt>invoke</tt>, <tt>execute</tt> always
+  executes the actions (without invoking or executing the prerequisites).
+
+file task (Rake::FileTask) ::
+  A file task is a task whose purpose is to create a file (which has the same
+  name as the task).  When invoked, a file task will only execute if one or
+  more of the following conditions are true.
+
+  1. The associated file does not exist.
+  2. A prerequisite has a later time stamp than the existing file.
+
+  Because normal Tasks always have the current time as timestamp, a FileTask
+  that has a normal Task prerequisite will always execute.
+
+invoke ::
+  When a task is invoked, first we check to see if it has been invoked before.
+  If it has been, then nothing else is done.  If this is the first time its
+  been invoked, then we invoke each of its prerequisites.  Finally, we check
+  to see if we need to execute the actions of this task by calling
+  Rake::Task#needed?.  Finally, if the task is needed, we execute its actions.
+
+  NOTE: Prerequisites are invoked even if the task is not needed.
+
+prerequisites ::
+  Every task has a set (possibly empty) of prerequisites.  A prerequisite P to
+  Task T is itself a task that must be invoked before Task T.
+
+rule ::
+  A rule is a recipe for synthesizing a task when no task is explicitly
+  defined.  Rules generally synthesize file tasks.
+
+task (Rake::Task) ::
+  Basic unit of work in a rakefile.  A task has a name, a set of prerequisites
+  and a list of actions to be performed.
 

data/lib/rake.rb

@@ -21,7 +21,7 @@
 #++
 
 module Rake
-  VERSION = '10.3.1'
+  VERSION = '10.3.2'
 end
 
 require 'rake/version'

data/lib/rake/application.rb

@@ -202,6 +202,10 @@ module Rake
     end
 
     def display_exception_details(ex) # :nodoc:
+      seen = Thread.current[:rake_display_exception_details_seen] ||= []
+      return if seen.include? ex
+      seen << ex
+
       display_exception_message_details(ex)
       display_exception_backtrace(ex)
       display_exception_details(ex.cause) if has_cause?(ex)

data/test/test_rake_application.rb

@@ -16,6 +16,72 @@ class TestRakeApplication < Rake::TestCase
     end
   end
 
+  def test_display_exception_details
+    begin
+      raise 'test'
+    rescue => ex
+    end
+
+    out, err = capture_io do
+      @app.display_error_message ex
+    end
+
+    assert_empty out
+
+    assert_match 'rake aborted!', err
+    assert_match __method__.to_s, err
+  end
+
+  def test_display_exception_details_cause
+    skip 'Exception#cause not implemented' unless
+      Exception.method_defined? :cause
+
+    begin
+      raise 'cause a'
+    rescue
+      begin
+        raise 'cause b'
+      rescue => ex
+      end
+    end
+
+    out, err = capture_io do
+      @app.display_error_message ex
+    end
+
+    assert_empty out
+
+    assert_match 'cause a', err
+    assert_match 'cause b', err
+  end
+
+  def test_display_exception_details_cause_loop
+    skip 'Exception#cause not implemented' unless
+      Exception.method_defined? :cause
+
+    begin
+      begin
+        raise 'cause a'
+      rescue => a
+        begin
+          raise 'cause b'
+        rescue
+          raise a
+        end
+      end
+    rescue => ex
+    end
+
+    out, err = capture_io do
+      @app.display_error_message ex
+    end
+
+    assert_empty out
+
+    assert_match 'cause a', err
+    assert_match 'cause b', err
+  end
+
   def test_display_tasks
     @app.options.show_tasks = :tasks
     @app.options.show_task_pattern = //

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: rake
 version: !ruby/object:Gem::Version
-  version: 10.3.1
+  version: 10.3.2
 platform: ruby
 authors:
 - Eric Hodel
@@ -30,7 +30,7 @@ cert_chain:
   pfkQPF5Ezsi73pEpFN93Fy21NKCYQH1jCwWeKUF29MIMGd6kE3ZmHW/7fz5GwKIM
   Ls5SgY48a0l7Hw==
   -----END CERTIFICATE-----
-date: 2014-04-17 00:00:00.000000000 Z
+date: 2014-05-16 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: minitest
@@ -104,6 +104,7 @@ executables:
 - rake
 extensions: []
 extra_rdoc_files:
+- CONTRIBUTING.rdoc
 - History.rdoc
 - Manifest.txt
 - README.rdoc
@@ -148,6 +149,7 @@ files:
 - ".gemtest"
 - ".rubocop.yml"
 - ".togglerc"
+- CONTRIBUTING.rdoc
 - History.rdoc
 - MIT-LICENSE
 - Manifest.txt