Don't show the stack trace on compilation error in build definition#2091
Don't show the stack trace on compilation error in build definition#2091
Conversation
|
Can one of the admins verify this patch? |
|
How does output for Would it be difficult to add test for this? Could you also add notes in the style of https://raw.githubusercontent.com/sbt/sbt/0.13/notes/0.13.9/distinct-rename.markdown |
|
Catching, logging and rethrowing looks like it would log more! |
|
Could you paste the session of what the user would see for |
If the user types @dwijnand Actually the exception is re-thrown without its stack trace |
|
Ah, that's so uncommon I completely missed it, nice. |
|
I think this LGTM. @jsuereth? |
|
This is merging into 0.13, but has release notes for 0.13.9. Do we want this to merge into 0.13.9, or alternatively should this be fore 0.13.10? |
|
And perhaps we should reference #2071 in the notes. |
There was a problem hiding this comment.
Sorry 1 more thing, you need a reference to 2071 above.
There was a problem hiding this comment.
That's fixed – Sorry for all these problems!
|
LGTM. Thanks. |
|
Thsi LGTM too. |
Don't show the stack trace on compilation error in build definition
This pull request hides the stack trace on compilation error in the build definition, as suggested in #2071.