Bug 159326 - [Viewers] Content Merge Viewer has ResourceBundle in constructor
Summary: [Viewers] Content Merge Viewer has ResourceBundle in constructor
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Compare (show other bugs)
Version: 3.2   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Compare-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-29 13:43 EDT by Bogdan Gheorghe CLA
Modified: 2019-09-06 15:31 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 Bogdan Gheorghe CLA 2006-09-29 13:43:14 EDT 
The Content Merge Viewer has a constructor where you have to pass in a ResourceBundle. The intent is to allow users to pass in different ResourceBundles in order to update common UI pieces. The problem is there is no way of knowing exactly *what* gets used by the viewer from the Resource Bundle. 

We need to look into what gets used by the Viewer and specify these in constants somewhere.
Comment 1 Michael Valenta CLA 2006-10-24 08:55:00 EDT 
Another option would be to deprecate the use of a bundle and come up with an alternative approach. we'll have to look at all the places wee the bundle is accessed to gain an understanding of the extensibility it provides.
Comment 2 Michael Valenta CLA 2007-04-18 21:46:30 EDT 
We didn't have time to address this in 3.3.
Comment 3 Eclipse Webmaster CLA 2019-09-06 15:31:56 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.