Community
Participate
Working Groups
I200412142000 - open a Messages CU - change getString() to getString1() (just by inserting the character 1) - save and build - open another CU that references getString() - try Ctrl-Click in that second CU (does not work) - change getString1() back to getString() in the first CU - save and build - try Ctrl-Click in the seconde CU -> does not work, which is unexpected
Addition from Christof: Ctrl+Click to be applied on NLS key. Just went through this and it worked. Christof please reopen with more details steps or a sample project.
- open JavaTextMessages from o.e.jdt.ui - change getString() declaration to getString1() - save and build - open ExperimentalProposal - navigate to compile error - ctrl-click on nls key -> does not work - expected - in JavaTextMessages change getString1() back to getString() - save and build - in ExperimentalProposal ctrl-click on nls key -> does not work - unexpected
Can still not reproduce (Christof witnessed). Keeping open and waiting for more details from Christof.
Created attachment 16647 [details] Project and steps to reproduce - start with a new workspace - close welcome view :-) - open Java perspective - create new 'Test' project with all default options - import attached project from archive with all default options - open SomeMessages.java - change getString() to getString1() - save - open Test.java -> ctrl-click on nls key does not work - expected - in SomeMessages.java change getString1() back to getString() - save -> ctrl-click on nls key in Test.java does not work - unexpected
Mmh. Needs to be investigated.
This is not related to nls tooling but is a bug in JCore. The key is actually that your class is called SearchMessages (package visible) and your file is called SearchMessage.java (no 's' at the end). Here's a smaller test case that illustrates the problem: 1. create a Java project 2. create CU X.java in package test (leave it open): package test; class Y { void foo() {} } 3. create class UseY in package test: package test; public class UseY { void use() { Y y= new Y(); y.foo(); } } 4. observe: no compile errors no temporary problems in editor 5. close both editors 6. open UseY ==> temporary error is shown: "Y cannot resolve to a type" 7. open CU X.java and switch back to UseY ==> temporary error goes away Resetting priortity and target milestone since the PR is moved to a different component.
*** This bug has been marked as a duplicate of 32505 ***
Verified for 3.2 using M20060629-1905.
