Bug 253508 - Message Bundles
Summary: Message Bundles
Status: RESOLVED FIXED
Alias: None
Product: EMFT
Classification: Modeling
Component: Releng (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P1 normal (vote)
Target Milestone: Past   Edit
Assignee: Nick Boldt CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 252795
  Show dependency tree
 
Reported: 2008-11-03 19:09 EST by Anne Jacko CLA
Modified: 2009-03-04 12:17 EST (History)
3 users (show)

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 Anne Jacko CLA 2008-11-03 19:09:11 EST 
+++ This bug was initially created as a clone of Bug #252795 +++

Projects must use Eclipse message bundles unless there are technical reasons not to. (see Message Bundle Conversion Tool and [1])
Comment 1 Laurent Goubet CLA 2008-12-10 07:55:14 EST 
All the Strings used throughout EMF Compare have been externalised in properties files using pure Java APIs (ResourceBundle) instead of Eclipse-specific APIs (NLS). This choice has been motivated by the stand-alone capabilities of EMF Compare : using Eclipse APIs would force us to have dependencies on eclipse/osgi jars.

This is the way we externalised our String for Ganymede and the community can still leverage the Babel project to localize message externalized through these APIs.

We think this as being a valid workaround for this bug, still pending for Ed Merks approval so that we can skip this Galileo must do in EMF Compare.
Comment 2 Ed Merks CLA 2009-03-04 12:17:49 EST 
EMF has at least three technical reasons for sticking with old Java resource
bundles, instead of adopting Eclipse message bundles.

1. To be able to run stand-alone (i.e. without any Eclipse dependencies).
2. To support API for accessing original, untranslated messages.
3. To allow message keys to be formed programatically (e.g. by including the
name of a class or feature).

So, we consider this requirement satisfied.