Rake version 0.9.4 contains a number of bug fixes.
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.
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.
Exit status with failing tests is not correctly set to non-zero.
Simplified syntax for phony task (for older versions of RDoc).
Stand alone FileList usage gets glob function (without loading in extra dependencies)
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.
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:
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 …
Tay Ray Chuan
Also, many thanks to Eric Hodel for assisting with getting this release out the door.
– Jim Weirich