I think we inherit --trace from rake. Might be worth looking if they have something like that already in place ?
On Tue, Mar 23, 2010 at 15:25, Rhett Sutphin <[email protected]>wrote: > I like the idea, but I think the environment variable is a bit clumsy and > hard to discover. What about a parameter for --trace? > > buildr --trace # traces everything > buildr --trace=tasks # traces just build-related bits -- task executions, > things logged with `trace` in buildr & extensions > buildr --trace=ant,javac # ups the verbosity for just ant and javac > > Rhett > > > On Mar 23, 2010, at 5:11 PM, Antoine Toulme wrote: > > I'm all for that one. I was for turning javac verbose to off by default so >> this looks more appropriate - more configuration for the ones that need >> it. >> >> On Tue, Mar 23, 2010 at 09:59, Alex Boisvert <[email protected] >> >wrote: >> >> This was brought up in another email but I figured it deserved a separate >>> thread. >>> >>> Right now "buildr --trace" turns the verbose fire-hose to full blast. >>> This >>> means we run "javac -verbose", "ant --trace", "apt -verbose", ... which >>> is >>> often overwhelming and of little use when you're simply debugging >>> Rake-related dependency issues. >>> >>> One solution would be to selectively turn on the trace switch based on >>> the >>> task so I was thinking of adding a BUILDR_TRACE environment variable that >>> would contain a list of comma-separated keywords to control tracing >>> behavior, e.g., export BUILDR_TRACE="javac,ant,apt". >>> >>> Any better ideas? >>> >>> alex >>> >>> >
