Add --backtrace option to see backtrace without seing the trace. #109

Merged
merged 1 commit into from Oct 17, 2012

Projects

None yet

4 participants

@grosser
Contributor
grosser commented Mar 31, 2012

It is then possible to have backtrace turned on all the time,
e.g. no re-running of failed tasks is necessary, without cluttering the output of successful rake tasks.

@grosser grosser Add --backtrace option to see the backtrace without seing the trace.
In a application it is then possible to have backtrace turned on all the time,
e.g. no re-running of failed tasks is necessary, without cluttering the output of successful rake tasks.
e90ce27
@nyarly
Contributor
nyarly commented May 19, 2012

This looks like a good fix for #105 - I'd like to see it included.

@grosser
Contributor
grosser commented Jun 27, 2012

@jimweirich can we have a merge plz ?

@urbanautomaton

I too would be very happy to see this feature added.

The comments in #105 are well made regarding fine-grained structuring of rake tasks, and in complex build systems undoubtedly the task chain is much more useful than the backtrace. However, rake sees a lot of use with Rails, where the dependency chains tend to be relatively simple, and failures are often buried in objects the rake task is talking to. This IMO makes the stacktrace relatively more valuable, and it would be nice to be able to have it displayed by default for failures without, as @grosser says, cluttering up the normal output.

@jimweirich jimweirich merged commit e90ce27 into jimweirich:master Oct 17, 2012
@jimweirich
Owner

Manually merged.

@grosser
Contributor
grosser commented Oct 17, 2012

Wow, thanks, already gave up on this getting in :D

@jimweirich
Owner

No problem. I was swamped with other stuff and neglected rake for a while. Now I'm trying to get a new release out in a timely manor.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment