Bug 259966 - [ErrorHandling] ErrorDialog does not properly format exception message in status
Summary: [ErrorHandling] ErrorDialog does not properly format exception message in status
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-05 11:24 EST by Markus Keller CLA
Modified: 2019-09-06 15:33 EDT (History)
2 users (show)

See Also:


Attachments
Screenshot (15.65 KB, image/png)
2009-01-05 11:24 EST, Markus Keller CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Keller CLA 2009-01-05 11:24:07 EST
Created attachment 121534 [details]
Screenshot

I20081217-1605

ErrorDialog does not properly exception message in status.

Steps:
- new workspace
- paste to Package Explorer:

package pack;
public class C {}
public class D {}

- copy _pasted_code_/src
- select _pasted_code_
- paste, use "src2" as new name

- File > Export... > Java > JAR File
- enter a destination
- click Finish

=> See the attached screenshot for the poorly formatted details area.
The second entry is an IStatus with:
- message= "Problem writing _pasted_code_/bin/pack/D.class to JAR: duplicate entry: pack/D.class" (id=8955)	
- exception= ZipException  (id=8954)	
	cause= ZipException  (id=8954)	
	detailMessage= "duplicate entry: pack/D.class" (id=8959)	
	stackTrace= null	

=> The third line in the details area should be indented in this case.
Comment 1 Susan McCourt CLA 2009-07-09 18:17:06 EDT
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 2 Eclipse Webmaster CLA 2019-09-06 15:33:05 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.