Community
Participate
Working Groups
- Have 2 classes which use the same NLSed strings. e.g. -------------------------------------------------------- public class A { void foo() { String s= Messages.A_0; String t= Messages.A_0; String u= Messages.A_1; } } public class B { void foo() { String s= Messages.A_0; String t= Messages.A_0; String u= Messages.A_1; } } -------------------------------------------------------- - Select 'A' in PE - Source -> Externalize strings - Internalize A_0 and A_1 => Class B is not updated resulting in compile errors - Select 'A' in PE - Source -> Externalize strings - Edit the names of the 2 keys A_0 and A_1 => Class B is not updated resulting in compile errors At least the user needs to be warned that the refactoring will result in compile errors.
The wizard currently only works in the scope of the given CU. > At least the user needs to be warned that the refactoring will result in > compile errors. If we add code to detect this then we should ask the user whether to internalize all occurrences or not.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
