-
Notifications
You must be signed in to change notification settings - Fork 613
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does nowrite
ever take effect?
#361
Comments
(For comparison, GNU Make's |
This also seems to make the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
--dry-run
sets bothnowrite(false)
andoptions.dry_run = true
. The thing is, so long asoptions.dry_run == true
, Task execution short-circuits before it ever gets to execute any FileUtils methods.So the question is... does
nowrite
/noop
ever take effect?The only way I can find to get Rake to tell me what it would do (without doing it) is:
$ rake -E 'Rake.nowrite(true)'
(That's the behavior I expected from
--dry-run
, honestly.)So... are the
noop
/nowrite
branches effectively dead code? Or am I missing something?The text was updated successfully, but these errors were encountered: