Bug 253507 - Message Bundles
Summary: Message Bundles
Status: CLOSED FIXED
Alias: None
Product: EMF
Classification: Modeling
Component: Releng (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P1 normal (vote)
Target Milestone: M4   Edit
Assignee: Nick Boldt CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 252795
  Show dependency tree
 
Reported: 2008-11-03 19:08 EST by Anne Jacko CLA
Modified: 2018-01-22 11:37 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:08:36 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 Christian Damus CLA 2008-11-12 14:40:32 EST 
Confirmed for the Query, Transaction, and Validation components.

The following message files all use the Equinox NLS message bundles:

org.eclipse.emf.query/src/org/eclipse/emf/query/internal/l10n/QueryMessages.properties
org.eclipse.emf.query.examples.ocl/src/org/eclipse/emf/query/examples/ocl/internal/l10n/QueryOCLMessages.properties
org.eclipse.emf.query.examples.statements/src/org/eclipse/emf/query/examples/statements/internal/l10n/QueryStatementsMessages.properties
org.eclipse.emf.transaction/src/org/eclipse/emf/transaction/internal/l10n/Messages.properties
org.eclipse.emf.transaction.ui/src/org/eclipse/emf/transaction/ui/internal/l10n/Messages.properties
org.eclipse.emf.validation/src/org/eclipse/emf/validation/internal/l10n/ValidationMessages.properties
org.eclipse.emf.validation.examples.general/src/org/eclipse/emf/validation/examples/general/internal/l10n/ValidationMessages.properties
org.eclipse.emf.validation.tests/src/org/eclipse/emf/validation/tests/l10n/messages.properties
org.eclipse.emf.validation.ui/src/org/eclipse/emf/validation/ui/internal/l10n/ValidationUIMessages.properties
org.eclipse.emf.validation.ui.ide/src/org/eclipse/emf/validation/ui/ide/internal/l10n/ValidationUIIDEMessages.properties
org.eclipse.emf.workspace/src/org/eclipse/emf/workspace/internal/l10n/Messages.properties
org.eclipse.emf.workspace.examples.library.editor/src/org/eclipse/emf/workspace/examples/extlibrary/internal/l10n/Messages.properties
Comment 2 Eike Stepper CLA 2008-12-11 15:29:04 EST 
CDO/Net4j are run-time technologies. All generic user interfaces are considered as usage examples. Therefor I always pulled the "technical reasons" card. Nevertheless I'll put it on my nice-to-have list.
Comment 3 Martin Taal CLA 2008-12-11 15:44:24 EST 
Same applies to Teneo
Comment 4 Dave Steinberg CLA 2008-12-11 16:55:02 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.
Comment 5 Ed Merks CLA 2018-01-22 11:37:03 EST 
Closing all fixed releng bugs.