Extended maintenance of Ruby 1.9.3 ended on February 23, 2015. Read more
Rake is invoked from the command line using:
% rake [<em>options</em> ...] [<em>VAR</em>=<em>VALUE</em>] [<em>targets</em> ...]
Set the environment variable name to value during the execution of the rake command. You can access the value by using ENV.
Import the Task, FileTask, and FileCreateTask into the top-level scope to
be compatible with older versions of Rake. Alternatively you can include
require 'rake/classic_namespace' in your Rakefile to
get the classic behavior.
Describe the tasks (matching optional PATTERN), then exit.
Do a dry run. Print the tasks invoked and executed, but do not actually execute any of the actions.
Execute some Ruby code and exit.
Execute some Ruby code, print the result, and exit.
Execute some Ruby code, then continue with normal task processing.
Display some help text and exit.
Add directory to the list of directories searched for require.
Do not search for a Rakefile in parent directories.
Display a list of all tasks and their immediate prerequisites.
Do not echo commands from FileUtils.
Use filename as the name of the rakefile. The default rakefile
rakefile taking precedence). If the rakefile is not found in
the current directory,
rake will search parent directories for
a match. The directory where the Rakefile is found will become the current
directory for the actions executed in the Rakefile.
Auto-import any .rake files in RAKELIBDIR. (default is ‘rakelib’)
Require name before executing the Rakefile.
Trace the rules resolution.
Like –quiet, but also suppresses the ‘in directory’ announcement.
Use the system wide (global) rakefiles. The project Rakefile is ignored. By default, the system wide rakefiles are used only if no project Rakefile is found. On Unix-like system, the system wide rake files are located in $HOME/.rake. On a windows system they are stored in $APPDATA/Rake.
Use the project level Rakefile, ignoring the system-wide (global) rakefiles.
Display a list of the major tasks and their comments. Comments are defined using the “desc” command.
Turn on invoke/execute tracing. Also enable full backtrace on errors.
Display a usage message and exit.
Echo the Sys commands to standard output.
Display the program version and exit.
In addition, any command line option of the form
VAR=VALUE will be added to the environment hash
ENV and may be tested in the Rakefile.