Forums
New posts
Search forums
Members
Current visitors
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Forums
Archive
Archive
Ruby
FileUtils writing to stderr
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
[QUOTE="Eric Hodel, post: 4677706"] or has occurred. For example I might have the following simple Note that rake's rm_rf is not exactly FileUtils' rm_rf Why? I expect informational messages on stderr. This way rake's messages don= 't interfere with a rake user's output. By having rake's messages on stderr a= rake task author can write tasks that can be piped to other commands. rake email | sendmail # for example (Yes, rake currently outputs a message on stdout. I have fixed that in trunk= ) ithin ant. Rake doesn't seem to return the correct error code so I was testi= ng for failure by detecting if anything was written to stderr. You should query $?, not stderr. Rake should be behaving like a standard uni= x command.=20 AFAIK rm -rf and mkdir -p always exit 0. What is your rake task that exits 0 improperly?= [/QUOTE]
Verification
Post reply
Forums
Archive
Archive
Ruby
FileUtils writing to stderr
Top