Browse files

Merge branch 'next-major-release'

* next-major-release: (24 commits)
  Tracing nil objects is ok.
  Add reference to release_notes in CHANGES.
  Remove commented code.
  handle nil objects in the output strings so the correct stack trace can be shown
  Bump to 10.0.3 and add release docs.
  Removed unused setting of REDUCE_COMPAT.
  Remove early return from deprecate.
  Add contrib/sys.rb back to shadow accidental inclusion from system.
  Add gempackagetask.rb back to shadow accidental inclusion from system.
  Shadow system rake/rdoctask to avoid accidental inclusion.
  Removed GONE failure.
  Bump to version 10.0.2.
  release doc for 10.0.2.
  Update the 10.0.1 release doc.
  Bump to 10.0.0
  require early time in Time extensions
  Update doc/release_notes/rake-10.0.0.rdoc
  bump to rake-10.0.0.beta.2
  non-file tasks now always report current time as timestamp
  tweek wording in release notes.
  • Loading branch information...
jimweirich committed Jan 23, 2013
2 parents 7bfa0f6 + 3fb4d20 commit 4188f9666975448a3d74d77b5a3065990347c071
@@ -1,5 +1,9 @@
= Rake Changelog
+NOTE: Refer to the individual release documents (in the
+ doc/release_notes directory) for changes after in version 0.9.4
+ and later.
== Master (for 0.9.3)
* The rake test loader now removes arguments it has processed. Issue #51
@@ -28,10 +28,6 @@ begin
rescue LoadError
-module Rake
- REDUCE_COMPAT = true if ARGV.include?("--reduce-compat")
require 'rake'
@@ -23,13 +23,6 @@ Options are:
stardard output. If _output_ is <tt>stderr</tt>, or if it is
missing, then the backtrace output is sent to standard error.
-[<tt>--classic-namespace</tt> (-n)]
- Import the Task, FileTask, and FileCreateTask into the top-level
- scope to be compatible with older versions of Rake. Alternatively
- you can include the line <code>require
- 'rake/classic_namespace'</code> in your Rakefile to get the
- classic behavior.
Used in combination with the -W options to force the output to
contain commented options only. This is the reverse of
@@ -102,16 +95,6 @@ Options are:
[<tt>--rakelibdir</tt> _rakelibdir_ (-R)]
Auto-import any .rake files in RAKELIBDIR. (default is 'rakelib')
- Remove the DSL commands from the Object inheritance hierarchy and
- do not define top level constants. This reduces the backwards
- compatibility of Rake, but allows rake to be used with software
- that would otherwise have conflicting definitions.
- *NOTE:* The next major version of Rake will only be able to be run
- in "reduce-compat" mode.
[<tt>--require</tt> _name_ (-r)]
Require _name_ before executing the Rakefile.
@@ -0,0 +1,178 @@
+= Rake 10.0 Released
+ "Jim, when will Rake reach version 1.0?"
+Over the past several years I've been asked that question at
+conferences, panels and over twitter. Due to historical reasons (or
+maybe just plain laziness) Rake has (incorrectly) been treating the
+second digit of the version as the major release number. So in my head
+Rake was already at version 9.
+Well, it's time to fix things. This next version of Rake drops old,
+crufty, backwards compatibility hacks such as top level constants, DSL
+methods defined in Object and numerous other features that are just no
+longer desired. It's also time to drop the leading zero from the
+version number as well and call this new version of rake what it
+really is: Version 10.
+So, welcome to Rake 10.0!
+Rake 10 is actually feature identical to the latest version of Rake 9
+(that would be the version spelled 0.9.3), *except* that Rake 10 drops
+all the sundry deprecated features that have accumulated over the years.
+If your Rakefile is up to date and current with all the new features
+of Rake 10, you are ready to go. If your Rakefile still uses a few
+deprecated feeatures, feel free to use Rake 9 (0.9.3) with the same
+feature set. Just be aware that future features will be in Rake 10
+family line.
+== Changes in 10.0
+As mentioned above, there are no new features in Rake 10. However,
+there are a number of features missing:
+* Classic namespaces are now gone. Rake is no longer able to reflect
+ the options settings in the global variables ($rakefile, $show_tasks,
+ $show_prereqs, $trace, $dryrun and $silent). The
+ <tt>--classic-namespace</tt> option is no longer supported.
+* Global constants are no longer supported. This includes
+ <tt>Task</tt>, <tt>FileTask</tt>, <tt>FileCreationTask</tt> and
+ <tt>RakeApp</tt>). The constant missing hook to warn about using
+ global rake constants has been removed.
+* The Rake DSL methods (task, file, directory, etc) are in their own
+ module (Rake::DSL). The stub versions of these methods (that printed
+ warnings) in Object have been removed. However, the DSL methods are
+ added to the top-level <tt>main</tt> object. Since <tt>main</tt> is
+ not in the inheritance tree, the presence of the DSL methods in main
+ should be low impact on other libraries.
+ If you want to use the Rake DSL commands from your own code, just
+ include <tt>Rake::DSL</tt> into your own classes and modules.
+* The deprecated syntax for task arguments (the one using
+ <tt>:needs</tt>) has been removed.
+* The <tt>--reduce-compat</tt> flag has been removed (it's not needed
+ anymore).
+* The deprecated <tt>rake/sys.rb</tt> library has been removed.
+* The deprecated <tt>rake/rdoctask.rb</tt> library has been removed.
+ RDoc supplies its own rake task now.
+* The deprecated <tt>rake/gempackagetask.rb</tt> library has been
+ removed. Gem supplies its own package task now.
+There is one small behavioral change:
+* Non-file tasks now always report the current time as their time
+ stamp. This is different from the previous behavior where non-file
+ tasks reported current time only if there were no prerequisites, and
+ the max prerequisite timestamp otherwise. This lead to inconsistent
+ and surprising behavior when adding prerequisites to tasks that in
+ turn were prequisites to file tasks. The new behavior is more
+ consistent and predictable.
+== Changes (from 0.9.3)
+Since Rake 10 includes the changes from the last version of Rake 9,
+we'll repeat the changes for version 0.9.3 here.
+=== New Features
+* Multitask tasks now use a thread pool. Use -j to limit the number of
+ available threads.
+* Use -m to turn regular tasks into multitasks (use at your own risk).
+* You can now do "Rake.add_rakelib 'dir'" in your Rakefile to
+ programatically add rake task libraries.
+* You can specific backtrace suppression patterns (see
+ --supress-backtrace)
+* Directory tasks can now take prerequisites and actions
+* Use --backtrace to request a full backtrace without the task trace.
+* You can say "--backtrace=stdout" and "--trace=stdout" to route trace
+ output to standard output rather than standard error.
+* Optional 'phony' target (enable with 'require 'rake/phony'") for
+ special purpose builds.
+* Task#clear now clears task comments as well as actions and
+ prerequisites. Task#clear_comment will specifically target comments.
+* The --all option will force -T and -D to consider all the tasks,
+ with and without descriptions.
+=== Bug Fixes
+* Semi-colons in windows rakefile paths now work.
+* Improved Control-C support when invoking multiple test suites.
+* egrep method now reads files in text mode (better support for
+ Windows)
+* Better deprecation line number reporting.
+* The -W option now works with all tasks, whether they have a
+ description or not.
+* File globs in rake should not be sorted alphabetically, independent
+ of file system and platform.
+* Numerous internal improvements.
+* Documentation typos and 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::
+GitHub:: git://
+== Thanks
+As usual, it was input from users that drove a lot of these changes. The
+following people contributed patches, made suggestions or made
+otherwise helpful comments. Thanks to ...
+* Aaron Patterson
+* Dylan Smith
+* Jo Liss
+* Jonas Pfenniger
+* Kazuki Tsujimoto
+* Michael Bishop
+* Michael Elufimov
+* Ryan Davis
+* Sam Grönblom
+* Sam Phippen
+* Sergio Wong
+* Tay Ray Chuan
+* grosser
+* quix
+Also, many thanks to Eric Hodel for assisting with getting this release
+out the door.
+-- Jim Weirich
Oops, something went wrong.

0 comments on commit 4188f96

Please sign in to comment.