| Summary: | Exception Cause lost (swallowed) in OSGILauncher | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Michael Vorburger <mike> |
| Component: | BIRT | Assignee: | Birt-ReportEngine-inbox <Birt-ReportEngine-inbox> |
| Status: | CLOSED DUPLICATE | QA Contact: | Hao Zhou <hao.zhou> |
| Severity: | normal | ||
| Priority: | P3 | CC: | bluesoldier, hustlg |
| Version: | 2.5.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
fixed in 3.7.0 *** This bug has been marked as a duplicate of bug 346984 *** |
At least in the 2.5.0 branch the OSGILauncher has a bug causing it to loose ("swallow") root cause Exception if there are any start-up issues: In http://dev.eclipse.org/viewcvs/viewvc.cgi/source/org.eclipse.birt.core/src/org/eclipse/birt/core/framework/osgi/OSGILauncher.java?view=markup&revision=1.19&root=BIRT_Project&pathrev=BIRT_2_5_0_Branch : line 95 of OSGILauncher should be changed from throw new CoreException( ex.getMessage( ), ex ); to throw new CoreException( ex.getMessage( ), new Object[0], ex ); Please see http://mifosforge.jira.com/browse/MIFOS-5119 for more. I've noticed that in the current HEAD that code was changed a bit, and this problem may not be there anymore, but I haven't tested it and thought I'd let you know about it anyways - if only to apply to some older maintenance branch where this still occurs, if you have any.