Comment 1 Laurent Goubet 2008-12-05 05:26:06 EST

All the Strings used throughout MTL have been externalised in properties files using pure Java APIs (ResourceBundle). We didn't use the Eclipse APIs since we provide a standalone mode and hence limit our use of Eclipse or third party jars.

Comment 2 Paul Elder 2008-12-12 15:14:36 EST

Laurent:

Can you provide potential users with information on the impact of this exemption. In particular:

1) What plug-ins would use standard Java message bundles?

2) How much extra memory will be consumed by used?

(Memory usage is the primary cost of using standard Java message bundles. Details on estimating the usage can be found at the page below).

http://dev.eclipse.org/viewcvs/index.cgi/platform-core-home/documents/3.1/message_bundles.html?view=co

Comment 3 Laurent Goubet 2008-12-15 05:40:27 EST

Hi Paul,

Yes, we are fully aware that pure Java APIs are way more expensive in memory than their Eclipse counterparts (what would be the need otherwise? :)).

As mentionned prior to this, we didn't use Eclise APIs as we do not use a single Eclipse plugin (well we do have one dependency to org.eclipse.core.runtime, though optional since it is only needed to make the compiler happy). Our choice is driven by our product's capabilities.

As for these questions :
1) All MTL plugins
2) Roughly 150KB overall

I should also note that we rely on EMF generated models, and as do we, EMF provides a standalone mode and generates pure Java message handling instead of its Eclipse-specific counterpart. 2) above does not take those Strings into account.

Comment 4 Paul Elder 2008-12-16 10:18:42 EST

Adding project lead approval for this exemption

Comment 5 Laurent Goubet 2009-01-28 05:29:40 EST

Fixing this bug as exemption has been approved. All MTL Strings are
externalized through pure java APIs.

Comment 6 Laurent Goubet 2010-07-26 09:18:32 EDT

This was part of the Ganymede release status tracking. Closing.