Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 345824 - [logging] no stack trace logged to error log
Summary: [logging] no stack trace logged to error log
Status: CLOSED FIXED
Alias: None
Product: TMF
Classification: Modeling
Component: Xtext (show other bugs)
Version: 2.0.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-14 16:03 EDT by Knut Wannheden CLA
Modified: 2017-09-19 17:57 EDT (History)
1 user (show)

See Also:

Attachments
proposed patch (1.31 KB, patch)
2011-05-14 16:03 EDT, Knut Wannheden CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Knut Wannheden CLA 2011-05-14 16:03:36 EDT 
Created attachment 195653 [details]
proposed patch

The EclipseLogAppender does not log potential stack traces to the Eclipse error log. Is that on purpose? I think that could be valuable for analyzing errors encountered by users.
Comment 1 Sven Efftinge CLA 2011-05-15 04:21:15 EDT 
please apply and push
Comment 2 Knut Wannheden CLA 2011-05-15 09:14:05 EDT 
pushed to master
Comment 3 Karsten Thoms CLA 2017-09-19 17:46:03 EDT 
Closing all bugs that were set to RESOLVED before Neon.0
Comment 4 Karsten Thoms CLA 2017-09-19 17:57:06 EDT 
Closing all bugs that were set to RESOLVED before Neon.0