rake 11.3.0 → 13.0.1

data/doc/release_notes/rake-0.7.0.rdoc

@@ -1,119 +0,0 @@
-= Rake 0.7.0 Released
-
-These changes for Rake have been brewing for a long time.  Here they
-are, I hope you enjoy them.
-
-== Changes
-
-=== New Features
-
-* Name space support for task names (see below).
-
-* Prerequisites can be executed in parallel (see below).
-
-* Added safe_ln support for openAFS (via Ludvig Omholt).
-
-* RDoc defaults to internal (in-process) invocation.  The old behavior
-  is still available by setting the +external+ flag to true.
-
-* Rakefiles are now loaded with the expanded path to prevent
-  accidental polution from the Ruby load path.
-
-* Task objects my now be used in prerequisite lists directly.
-
-* Task objects (in addition to task names) may now be included in the
-  prerequisite list of a task.
-
-* Internals cleanup and refactoring.
-
-=== Bug Fixes
-
-* Compatibility fixes for Ruby 1.8.4 FileUtils changes.
-
-=== Namespaces
-
-Tasks can now be nested inside their own namespaces.  Tasks within one
-namespace will not accidently interfer with tasks named in a different
-namespace.
-
-For example:
-
-  namespace "main" do
-    task :build do
-      # Build the main program
-    end
-  end
-
-  namespace "samples" do
-    task :build do
-      # Build the sample programs
-    end
-  end
-
-  task :build_all => ["main:build", "samples:build"]
-
-Even though both tasks are named :build, they are separate tasks in
-their own namespaces.  The :build_all task (defined in the toplevel
-namespace) references both build tasks in its prerequisites.
-
-You may invoke each of the individual build tasks with the following
-commands:
-
-  rake main:build
-  rake samples:build
-
-Or invoke both via the :build_all command:
-
-  rake build_all
-
-Namespaces may be nested arbitrarily.  Since the name of file tasks
-correspond to the name of a file in the external file system,
-FileTasks are not affected by the namespaces.
-
-See the Rakefile format documentation (in the Rake API documents) for
-more information.
-
-=== Parallel Tasks
-
-Sometimes you have several tasks that can be executed in parallel.  By
-specifying these tasks as prerequisites to a +multitask+ task.
-
-In the following example the tasks copy_src, copy_doc and copy_bin
-will all execute in parallel in their own thread.
-
-  multitask :copy_files => [:copy_src, :copy_doc, :copy_bin] do
-    puts "All Copies Complete"
-  end
-
-== What is Rake
-
-Rake is a build tool similar to the make program in many ways.  But
-instead of cryptic make recipes, Rake uses standard Ruby code to
-declare tasks and dependencies.  You have the full power of a modern
-scripting language built right into your build tool.
-
-== Availability
-
-The easiest way to get and install rake is via RubyGems ...
-
-  gem install rake    (you may need root/admin privileges)
-
-Otherwise, you can get it from the more traditional places:
-
-Home Page:: http://rake.rubyforge.org/
-Download::  http://rubyforge.org/project/showfiles.php?group_id=50
-
-== Thanks
-
-As usual, it was input from users that drove a alot of these changes.
-The following people either contributed patches, made suggestions or
-made otherwise helpful comments.  Thanks to ...
-
-* Doug Young (inspriation for the parallel task)
-
-* David Heinemeier Hansson (for --trace message enhancement and for
-  pushing for namespace support).
-
-* Ludvig Omholt (for the openAFS fix)
-
--- Jim Weirich

data/doc/release_notes/rake-0.7.1.rdoc

@@ -1,59 +0,0 @@
-= Rake 0.7.1 Released
-
-Version 0.7.1 supplies a bug fix and a few minor enhancements.
-
-== Changes
-
-=== Bug Fixes in 0.7.1
-
-* Changes in the exception reported for the FileUtils.ln caused
-  safe_ln to fail with a NotImplementedError.  Rake 0.7.1 will now
-  catch that error or any StandardError and properly fall back to
-  using +cp+.
-
-=== New Features in 0.7.1
-
-* You can filter the results of the --task option by supplying an
-  optional regular expression.  This allows the user to easily find a
-  particular task name in a long list of possible names.
-
-* Transforming procs in a rule may now return a list of prerequisites.
-  This allows more flexible rule formation.
-
-* FileList and String now support a +pathmap+ melthod that makes the
-  transforming paths a bit easier.  See the API docs for +pathmap+ for
-  details.
-
-* The -f option without a value will disable the search for a
-  Rakefile.  This allows the Rakefile to be defined entirely in a
-  library (and loaded with the -r option).  The current working
-  directory is not changed when this is done.
-
-== What is Rake
-
-Rake is a build tool similar to the make program in many ways.  But
-instead of cryptic make recipes, Rake uses standard Ruby code to
-declare tasks and dependencies.  You have the full power of a modern
-scripting language built right into your build tool.
-
-== Availability
-
-The easiest way to get and install rake is via RubyGems ...
-
-  gem install rake    (you may need root/admin privileges)
-
-Otherwise, you can get it from the more traditional places:
-
-Home Page:: http://rake.rubyforge.org/
-Download::  http://rubyforge.org/project/showfiles.php?group_id=50
-
-== Thanks
-
-As usual, it was input from users that drove a alot of these changes.
-The following people either contributed patches, made suggestions or
-made otherwise helpful comments.  Thanks to ...
-
-* James Britt and Assaph Mehr for reporting and helping to debug the
-  safe_ln issue.
-
--- Jim Weirich

data/doc/release_notes/rake-0.7.2.rdoc

@@ -1,121 +0,0 @@
-= Rake 0.7.2 Released
-
-Version 0.7.2 supplies a bug fix and a few minor enhancements.  In
-particular, the new version fixes an incompatibility with the soon to
-be released Ruby 1.8.6.  We strongly recommend upgrading to Rake 0.7.2
-in order to be compatible with the new version of Ruby.
-
-== Changes
-
-=== Bug Fixes in 0.7.2
-
-There are quite a number of bug fixes in the new 0.7.2 version of
-Rake:
-
-* Removed dependency on internal fu_xxx functions from FileUtils.
-
-* Error messages are now send to stderr rather than stdout (from
-  Payton Quackenbush).
-
-* Better error handling on invalid command line arguments (from Payton
-  Quackenbush).
-
-* Fixed some bugs where the application object was going to the global
-  appliation instead of using its own data.
-
-* Fixed the method name leak from FileUtils (bug found by Glenn
-  Vanderburg).
-
-* Added test for noop, bad_option and verbose flags to sh command.
-
-* Added a description to the gem task in GemPackageTask.
-
-* Fixed a bug when rules have multiple prerequisites (patch by Joel
-  VanderWerf)
-
-* Added the handful of RakeFileUtils to the private method as well.
-
-=== New Features in 0.7.2
-
-The following new features are available in Rake version 0.7.2:
-
-* Added square and curly bracket patterns to FileList#include (Tilman
-  Sauerbeck).
-
-* FileLists can now pass a block to FileList#exclude to exclude files
-  based on calculated values.
-
-* Added plain filename support to rule dependents (suggested by Nobu
-  Nakada).
-
-* Added pathmap support to rule dependents.  In other words, if a
-  pathmap format (beginning with a '%') is given as a Rake rule
-  dependent, then the name of the depend will be the name of the
-  target with the pathmap format applied.
-
-* Added a 'tasks' method to a namespace to get a list of tasks
-  associated with the namespace.
-
-* Added tar_command and zip_command options to the Package task.
-
-* The clean task will no longer delete 'core' if it is a directory.
-
-=== Internal Rake Improvements
-
-The following changes will are mainly internal improvements and
-refactorings and have little effect on the end user.  But they may be
-of interest to the general public.
-
-* Added rcov task and updated unit testing for better code coverage.
-
-* Added a 'shame' task to the Rakefile.
-
-* Added rake_extension to handle detection of extension collisions.
-
-* Added a protected 'require "rubygems"' to test/test_application to
-  unbreak cruisecontrol.rb.
-
-* Removed rake_dup.  Now we just simply rescue a bad dup.
-
-* Refactored the FileList reject logic to remove duplication.
-
-* Removed if __FILE__ at the end of the rake.rb file.
-
-== What is Rake
-
-Rake is a build tool similar to the make program in many ways.  But
-instead of cryptic make recipes, Rake uses standard Ruby code to
-declare tasks and dependencies.  You have the full power of a modern
-scripting language built right into your build tool.
-
-== Availability
-
-The easiest way to get and install rake is via RubyGems ...
-
-  gem install rake    (you may need root/admin privileges)
-
-Otherwise, you can get it from the more traditional places:
-
-Home Page:: http://rake.rubyforge.org/
-Download::  http://rubyforge.org/project/showfiles.php?group_id=50
-
-== Thanks
-
-As usual, it was input from users that drove a alot of these changes.
-The following people either contributed patches, made suggestions or
-made otherwise helpful comments.  Thanks to ...
-
-* Payton Quackenbush -- For several error handling improvements.
-
-* Glenn Vanderburg -- For finding and fixing the method name leak from
-  FileUtils.
-
-* Joel VanderWerf -- for finding and fixing a bug in the handling of
-  multiple prerequisites.
-
-* Tilman Sauerbeck -- For some enhancing FileList to support more
-  advanced file globbing.
-
-* Nobu Nakada -- For suggesting plain file name support to rule dependents.
-
--- Jim Weirich

data/doc/release_notes/rake-0.7.3.rdoc

@@ -1,47 +0,0 @@
-= Rake 0.7.3 Released
-
-Rake version 0.7.3 is a minor release that includes some refactoring to better
-support custom Rake applications.
-
-== Changes
-
-=== New Features in Version 0.7.3
-
-* Added the +init+ and +top_level+ methods to make the creation of custom Rake applications a bit easier.  E.g.
-
-    gem 'rake', ">= 0.7.3"
-    require 'rake'
-
-    Rake.application.init('myrake')
-
-    task :default do
-      something_interesting
-    end
-
-    Rake.application.top_level
-
-== What is Rake
-
-Rake is a build tool similar to the make program in many ways. But instead of
-cryptic make recipes, Rake uses standard Ruby code to declare tasks and
-dependencies. You have the full power of a modern scripting language built
-right into your build tool.
-
-== Availability
-
-The easiest way to get and install rake is via RubyGems ...
-
-  gem install rake    (you may need root/admin privileges)
-
-Otherwise, you can get it from the more traditional places:
-
-Home Page:: http://rake.rubyforge.org/
-Download::  http://rubyforge.org/project/showfiles.php?group_id=50
-
-== Thanks
-
-As usual, it was input from users that drove a alot of these changes. The
-following people either contributed patches, made suggestions or made
-otherwise helpful comments. Thanks to ...
-
--- Jim Weirich

data/doc/release_notes/rake-0.8.0.rdoc

@@ -1,114 +0,0 @@
-= Rake 0.8.0/0.8.1 Released
-
-Rake version 0.8.0 is a new release of rake that includes serveral new
-features.
-
-== Changes
-
-=== New Features in Version 0.8.0
-
-* Tasks can now receive command line parameters.  See the examples
-  below for more details.
-
-* Comments are limited to 80 columns on output, but full comments can
-  be seen by using the -D parameter. (feature suggested by Jamis
-  Buck).
-
-* Explicit exit(n) calls will now set the exit status to n. (patch
-  provided by Stephen Touset).
-
-* Rake is now compatible with Ruby 1.9.
-
-Version 0.8.1 is a minor update that includes additional Ruby 1.9
-compatibility fixes.
-
-== What is Rake
-
-Rake is a build tool similar to the make program in many ways. But
-instead of cryptic make recipes, Rake uses standard Ruby code to
-declare tasks and dependencies. You have the full power of a modern
-scripting language built right into your build tool.
-
-== Availability
-
-The easiest way to get and install rake is via RubyGems ...
-
-  gem install rake    (you may need root/admin privileges)
-
-Otherwise, you can get it from the more traditional places:
-
-Home Page:: http://rake.rubyforge.org/
-Download::  http://rubyforge.org/project/showfiles.php?group_id=50
-
-== Task Argument Examples
-
-Prior to version 0.8.0, rake was only able to handle command line
-arguments of the form NAME=VALUE that were passed into Rake via the
-ENV hash.  Many folks had asked for some kind of simple command line
-arguments, perhaps using "--" to separate regular task names from
-argument values on the command line.  The problem is that there was no
-easy way to associate positional arguments on the command line with
-different tasks.  Suppose both tasks :a and :b expect a command line
-argument: does the first value go with :a?  What if :b is run first?
-Should it then get the first command line argument.
-
-Rake 0.8.0 solves this problem by explicitly passing values directly
-to the tasks that need them.  For example, if I had a release task
-that required a version number, I could say:
-
-   rake release[0.8.0]
-
-And the string "0.8.0" will be passed to the :release task.  Multiple
-arguments can be passed by separating them with a comma, for example:
-
-   rake name[john,doe]
-
-Just a few words of caution.  The rake task name and its arguments
-need to be a single command line argument to rake.  This generally
-means no spaces.  If spaces are needed, then the entire rake +
-argument string should be quoted.  Something like this:
-
-   rake "name[billy bob, smith]"
-
-(Quoting rules vary between operating systems and shells, so make sure
-you consult the proper docs for your OS/shell).
-
-=== Tasks that Expect Parameters
-
-Parameters are only given to tasks that are setup to expect them.  In
-order to handle named parameters, the task declaration syntax for
-tasks has been extended slightly.
-
-For example, a task that needs a first name and last name might be
-declared as:
-
-   task :name, :first_name, :last_name
-
-The first argument is still the name of the task (:name in this case).
-The next to argumements are the names of the parameters expected by
-:name (:first_name and :last_name in the example).
-
-To access the values of the paramters, the block defining the task
-behaviour can now accept a second parameter:
-
-   task :name, :first_name, :last_name do |t, args|
-     puts "First name is #{args.first_name}"
-     puts "Last  name is #{args.last_name}"
-   end
-
-The first argument of the block "t" is always bound to the current
-task object.  The second argument "args" is an open-struct like object
-that allows access to the task arguments.  Extra command line
-arguments to a task are ignored.  Missing command line arguments are
-given the nil value.
-
-== Thanks
-
-As usual, it was input from users that drove a alot of these changes. The
-following people either contributed patches, made suggestions or made
-otherwise helpful comments.  Thanks to ...
-
-* Jamis Buck (for comment formatting suggestions)
-* Stephen Touset (for exit status patch).
-
--- Jim Weirich