RubyGems - rubyjobbuilderdsl - Versions diffs - 0.0.2 → 0.0.3 - Mend

rubyjobbuilderdsl 0.0.2 → 0.0.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (1263) hide show

data/vendor/bundle/ruby/2.1.0/gems/rake-0.9.6/doc/release_notes/rake-0.4.14.rdoc DELETED Viewed

@@ -1,23 +0,0 @@
-= Rake 0.4.14 Released
-== Changes
-Version 0.4.14 is a compatibility fix to allow Rake's test task to
-work under Ruby 1.8.2.  A change in the Test::Unit autorun feature
-prevented Rake from running any tests.  This release fixes the
-problem.
-Rake 0.4.14 is the recommended release for anyone using Ruby 1.8.2.
-== 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
-Home Page:: http://rake.rubyforge.org/
-Download::  http://rubyforge.org/project/showfiles.php?group_id=50

data/vendor/bundle/ruby/2.1.0/gems/rake-0.9.6/doc/release_notes/rake-0.4.15.rdoc DELETED Viewed

@@ -1,35 +0,0 @@
-= Rake 0.4.15 Released
-== Changes
-Version 0.4.15 is a bug fix update for the Ruby 1.8.2 compatibility
-changes.  This release includes:
-* Fixed a bug that prevented the TESTOPTS flag from working with the
-  revised for 1.8.2 test task.
-* Updated the docs on --trace to indicate that it also enables a full
-  backtrace on errors.
-* Several fixes for new warnings generated.
-== Mini-Roadmap
-I will continue to issue Rake updates in the 0.4.xx series as new
-Ruby-1.8.2 issues become manifest.  Once the codebase stabilizes, I
-will release a 0.5.0 version incorporating all the changes.  If you
-are not using Ruby-1.8.2 and wish to avoid version churn, I recommend
-staying with a release prior to Rake-0.4.14.
-== 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
-Home Page:: http://rake.rubyforge.org/
-Download::  http://rubyforge.org/project/showfiles.php?group_id=50

data/vendor/bundle/ruby/2.1.0/gems/rake-0.9.6/doc/release_notes/rake-0.5.0.rdoc DELETED Viewed

@@ -1,53 +0,0 @@
-= Rake 0.5.0 Released
-It has been a long time in coming, but we finally have a new version
-of Rake available.
-== Changes
-* Fixed bug where missing intermediate file dependencies could cause
-  an abort with --trace or --dry-run.  (Brian Candler)
-* Recursive rules are now supported (Tilman Sauerbeck).
-* Added tar.gz and tar.bz2 support to package task (Tilman Sauerbeck).
-* Added warning option for the Test Task (requested by Eric Hodel).
-* The jamis rdoc template is only used if it exists.
-* Added fix for Ruby 1.8.2 test/unit and rails problem.
-* Added contributed rake man file. (Jani Monoses)
-* Fixed documentation that was lacking the Rake module name (Tilman
-  Sauerbeck).
-== 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
-Lots of people provided input to this release.  Thanks to Tilman
-Sauerbeck for numerous patches, documentation fixes and suggestions.
-And for also pushing me to get this release out.  Also, thanks to
-Brian Candler for the finding and fixing --trace/dry-run fix.  That
-was an obscure bug.  Also to Eric Hodel for some good suggestions.
--- Jim Weirich

data/vendor/bundle/ruby/2.1.0/gems/rake-0.9.6/doc/release_notes/rake-0.5.3.rdoc DELETED Viewed

@@ -1,78 +0,0 @@
-= Rake 0.5.0 Released
-Although it has only been two weeks since the last release, we have
-enough updates to the Rake program to make it time for another
-release.
-== Changes
-Here are the changes for version 0.5.3 ...
-* FileLists have been extensively changed so that they mimic the
-  behavior of real arrays even more closely.  In particular,
-  operations on FileLists that return a new collection (e.g. collect,
-  reject) will now return a FileList rather than an array.  In
-  addition, several places where FileLists were not properly expanded
-  before use have been fixed.
-* A method (+ext+) to simplify the handling of file extensions was
-  added to String and to Array.
-* The 'testrb' script in test/unit tends to silently swallow syntax
-  errors in test suites.  Because of that, the default test loader is
-  now a rake-provided script.  You can still use 'testrb' by setting
-  the loader flag in the test task to :testrb.  (See the API documents
-  for TestTask for all the loader flag values).
-* FileUtil methods (e.g. cp, mv, install) are now declared to be
-  private.  This will cut down on the interference with user defined
-  methods of the same name.
-* Fixed the verbose flag in the TestTask so that the test code is
-  controlled by the flag.  Also shortened up some failure messages.
-  (Thanks to Tobias Luetke for the suggestion).
-* Rules will now properly detect a task that can generate a source
-  file.  Previously rules would only consider source files that were
-  already present.
-* Added an +import+ command that allows Rake to dynamically import
-  dependendencies into a running Rake session.  The +import+ command
-  can run tasks to update the dependency file before loading them.
-  Dependency files can be in rake or make format, allowing rake to
-  work with tools designed to generate dependencies for make.
-== 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.
-Thanks to ...
-* Brian Gernhardt for the rules fix (especially for the patience to
-  explain the problem to me until I got what he was talking about).
-* Stefan Lang for pointing out problems in the dark corners of the
-  FileList implementation.
-* Alexey Verkhovsky pointing out the silently swallows syntax errors
-  in tests.
-* Tobias Luetke for beautifying the test task output.
-* Sam Roberts for some of the ideas behind dependency loading.
--- Jim Weirich

data/vendor/bundle/ruby/2.1.0/gems/rake-0.9.6/doc/release_notes/rake-0.5.4.rdoc DELETED Viewed

@@ -1,46 +0,0 @@
-= Rake 0.5.4 Released
-Time for some minor bug fixes and small enhancements
-== Changes
-Here are the changes for version 0.5.3 ...
-* Added double quotes to the test runner.  This allows the location of
-  the tests (and runner) to be in a directory path that contains
-  spaces (e.g. "C:/Program Files/ruby/bin").
-* Added .svn to default ignore list.  Now subversion project metadata
-  is automatically ignored by Rake's FileList.
-* Updated FileList#include to support nested arrays and filelists.
-  FileLists are flat lists of file names.  Using a FileList in an
-  include will flatten out the nested file names.
-== 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.
-Thanks to ...
-* Tilman Sauerbeck for the nested FileList suggestion.
-* Josh Knowles for pointing out the spaces in directory name problem.
--- Jim Weirich

data/vendor/bundle/ruby/2.1.0/gems/rake-0.9.6/doc/release_notes/rake-0.6.0.rdoc DELETED Viewed

@@ -1,141 +0,0 @@
-= Rake 0.6.0 Released
-Its time for some long requested enhancements and lots of bug fixes
-... And a whole new web page.
-== New Web Page
-The primary documentation for rake has moved from the RubyForge based
-wiki to its own Hieraki based web site.  Constant spam on the wiki
-made it a difficult to keep clean.  The new site will be easier to
-update and organize.
-Check out the new documentation at: http://docs.rubyrake.org
-We will be adding new documentation to the site as time goes on.
-In addition to the new docs page, make sure you check out Martin
-Fowlers article on rake at http://martinfowler.com/articles/rake.html
-== Changes
-=== New Features
-* Multiple prerequisites on Rake rules now allowed.  However, keep the
-  following in mind:
-  1. All the prerequisites of a rule must be available before a rule
-     is triggered, where "enabled" means (a) an existing file, (b) a
-     defined rule, or (c) another rule which also must be
-     trigger-able.
-  2. Rules are checked in order of definition, so it is important to
-     order your rules properly.  If a file can be created by two
-     different rules, put the more specific rule first (otherwise the
-     more general rule will trigger first and the specific one will
-     never be triggered).
-  3. The <tt>source</tt> method now returns the name of the first
-     prerequisite listed in the rule.  <tt>sources</tt> returns the
-     names of all the rule prerequisites, ordered as they are defined
-     in the rule.  If the task has other prerequisites not defined in
-     the rule (but defined in an explicit task definition), then they
-     will _not_ be included in the sources list.
-* FileLists may now use the egrep command.  This popular enhancement
-  is now a core part of the FileList object.  If you want to get a
-  list of all your to-dos, fixmes and TBD comments, add the following
-  to your Rakefile.
-    desc "Look for TODO and FIXME tags in the code"
-    task :todo do
-      FileList['**/*.rb'].egrep /#.*(FIXME|TODO|TBD)/
-    end
-* The <tt>investigation</tt> method was added to task object to dump
-  out some important values.  This makes it a bit easier to debug Rake
-  tasks.
-  For example, if you are having problems with a particular task, just
-  print it out:
-    task :huh do
-      puts Rake::Task['huh'].investigation
-    end
-* The Rake::TestTask class now supports a "ruby_opts" option to pass
-  arbitrary ruby options to a test subprocess.
-=== Some Incompatibilities
-* When using the <tt>ruby</tt> command to start a Ruby subprocess, the
-  Ruby interpreter that is currently running rake is used by default.
-  This makes it easier to use rake in an environment with multiple
-  ruby installation.  (Previously, the first ruby command found in the
-  PATH was used).
-  If you wish to chose a different Ruby interpreter, you can
-  explicitly choose the interpreter via the <tt>sh</tt> command.
-* The major rake classes (Task, FileTask, FileCreationTask, RakeApp)
-  have been moved out of the toplevel scope and are now accessible as
-  Rake::Task, Rake::FileTask, Rake::FileCreationTask and
-  Rake::Application.  If your Rakefile
-  directly references any one of these tasks, you may:
-  1. Update your Rakefile to use the new classnames
-  2. Use the --classic-namespace option on the rake command to get the
-     old behavior,
-  3. Add <code>require 'rake/classic_namespace'</code> to the
-     Rakefile to get the old behavior.
-  <tt>rake</tt> will print a rather annoying warning whenever a
-  deprecated class name is referenced without enabling classic
-  namespace.
-=== Bug Fixes
-* Several unit tests and functional tests were fixed to run better
-  under windows.
-* Directory tasks are now a specialized version of a File task.  A
-  directory task will only be triggered if it doesn't exist.  It will
-  not be triggered if it is out of date w.r.t. any of its
-  prerequisites.
-* Fixed a bug in the Rake::GemPackageTask class so that the gem now
-  properly contains the platform name.
-* Fixed a bug where a prerequisite on a <tt>file</tt> task would cause
-  an exception if the prerequisite did not exist.
-== 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 ...
-* Greg Fast (better ruby_opt test options)
-* Kelly Felkins (requested by better namespace support)
-* Martin Fowler (suggested Task.investigation)
-* Stuart Jansen (send initial patch for multiple prerequisites).
-* Masao Mutch (better support for non-ruby Gem platforms)
-* Philipp Neubeck (patch for file task exception fix)
--- Jim Weirich

data/vendor/bundle/ruby/2.1.0/gems/rake-0.9.6/doc/release_notes/rake-0.7.0.rdoc DELETED Viewed

@@ -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/vendor/bundle/ruby/2.1.0/gems/rake-0.9.6/doc/release_notes/rake-0.7.1.rdoc DELETED Viewed

@@ -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/vendor/bundle/ruby/2.1.0/gems/rake-0.9.6/doc/release_notes/rake-0.7.2.rdoc DELETED Viewed

@@ -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