Bug 191928 - Use Util.log instead of printStackTrace at AbstractImageBuilder#612
Summary: Use Util.log instead of printStackTrace at AbstractImageBuilder#612
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.3   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: 3.4 M1   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-11 07:24 EDT by Maxime Daniel CLA
Modified: 2007-08-03 10:30 EDT (History)
0 users

See Also:

Attachments
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 Maxime Daniel CLA 2007-06-11 07:24:23 EDT 
Source code based, v_770.

Noticed that we used printStackTrace here instead of Util.log (what we do in other places in the package when we want to log the exception). Discussed with Kent who sees no (good) reason to do so.
Hence we should call Util.log there.

(Not conduced a systematic search upon all our sources yet, but this would be needed as well.)
Comment 1 Kent Johnson CLA 2007-06-26 10:50:07 EDT 
Switched 2 calls in AbstractImageBuilder & IncrementalImageBuilder
Comment 2 Frederic Fusier CLA 2007-08-03 10:30:32 EDT 
Verified (with v_804 code) for 3.4M1 using build I20070802-0800.