Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 338524 - Avoid using class MessageFormat
Summary: Avoid using class MessageFormat
Status: VERIFIED FIXED
Alias: None
Product: Objectteams
Classification: Tools
Component: OTDT (show other bugs)
Version: 0.8   Edit
Hardware: Other Linux
: P3 normal (vote)
Target Milestone: 0.8 M6   Edit
Assignee: Stephan Herrmann CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-01 06:39 EST by Stephan Herrmann CLA
Modified: 2011-06-07 09:50 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 Stephan Herrmann CLA 2011-03-01 06:39:19 EST 
The rules for the simultaneous release require
 "Excel in NL support. The Project must use ICU4J, where appropriate, 
  to excel in NL support."
Scanning the documentation I found one class that should be avoided and is 
actually in use by the OTDT: java.text.MessageFormat.

This should be fixed by simply switching to org.eclipse.osgi.util.NLS.
Still, care must be taken that no classes of the batch compiler have
a dependency on osgi.
Comment 1 Stephan Herrmann CLA 2011-03-01 09:39:41 EST 
Resolved in a big clean-up (revisions 1340 - 1348).
Comment 2 Stephan Herrmann CLA 2011-03-01 09:40:43 EST 
.
Comment 3 Stephan Herrmann CLA 2011-06-07 09:50:35 EDT 
Verified by search over source code:
no more references to java.text.MessageFormat in our code.