|
Re: externalized strings : conver to 'eclipse mechanism' [message #335362 is a reply to message #335361] |
Fri, 03 April 2009 17:51 |
Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
On 4/3/2009 1:18 PM, Edoardo Comar wrote:
> Hi
>
> is there a recommended way to change already externalized strings to use
> the 'eclipse mechanism' (i.e. Messages extends NLS ...) rather than the
> default one ?
>
> I think that the "eclipse mechanism" is better due to not having
> literals left in code (hence far fewer //$NON-NLS-1$) and easy junit
> testability for broken keys.
A follow-up question: why is the default in the Externalize Strings
wizard still to NOT use the "Eclipse mechanism" (at least as of 3.4.2)?
Is there a bug report about that already?
Eric
|
|
|
|
|
Re: externalized strings : conver to 'eclipse mechanism' [message #335413 is a reply to message #335379] |
Mon, 06 April 2009 20:16 |
Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
On 4/5/2009 6:12 AM, Daniel Megert wrote:
> Eric Rizzo wrote:
>> A follow-up question: why is the default in the Externalize Strings
>> wizard still to NOT use the "Eclipse mechanism" (at least as of
>> 3.4.2)? Is there a bug report about that already?
> It should definitely remember your last choice which it currently
> doesn't and given we already test whether org.eclipse.osgi is on the
> build path we could also change the default. Can you file a bug against
> JDT UI?
Done:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=271375
I might even find time to submit a patch for it later this week, but no
promises.
Eric
|
|
|
Powered by
FUDForum. Page generated in 0.03925 seconds