Bug 90450 - [nls tooling] Externalizing Strings to two bundles
Summary: [nls tooling] Externalizing Strings to two bundles
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P5 enhancement with 2 votes (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-06 09:43 EDT by Hosam CLA
Modified: 2007-06-22 10:02 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 Hosam CLA 2005-04-06 09:43:21 EDT 
I'm using Eclipse 3.1M5a.

I'm using two bundles for externalization; one is general for the whole project
and another one for each package. Eclipse makes it a pain to do such a thing.
After externalizing some strings to one bundle, using the "Externalize Strings"
feature would cause ALL strings to be removed the first bundle, even if I mark
them to be ignored. In addition, ignoring already-externalized strings would
remove the "Messages.getString", and replace them with the original strings from
the resource bundle.
Comment 1 Olivier Thomann CLA 2005-04-06 11:33:04 EDT 
Move to JDT/UI
Comment 2 Jean-Yves TOUMIT CLA 2005-04-19 07:26:57 EDT 
I have the same problem. It's impossible to use two property bundles for a
single class, and that's a real pain I must say, when you really want to
separate strings depending on their use.
Comment 3 Jean-Yves TOUMIT CLA 2005-04-19 07:28:39 EDT 
By the way, I'm using Eclipse 3.0.2.
Comment 4 Dani Megert CLA 2006-03-21 04:56:27 EST 
Currently not planned.
Comment 5 Dani Megert CLA 2007-06-22 09:59:23 EDT 
Get rid of deprecated state.