Bug 388112

Summary:	[nls tooling] Wrong NLS key reference found when a constant with same name exists
Product:	[Eclipse Project] JDT	Reporter:	Dani Megert <daniel_megert>
Component:	Text	Assignee:	JDT-Text-Inbox <jdt-text-inbox>
Status:	ASSIGNED ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	deepakazad
Version:	3.7
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:	stalebug
Bug Depends on:	83061
Bug Blocks:

Description Dani Megert

2012-08-27 09:42:34 EDT

Got broken during 3.7 by fix for bug 83061.

1. paste this:
public class Main {
	private static String HI="bug";
    public static void main(String[] args) {
    	System.out.println("HI");
    	System.out.println(HI);
    }
}

2. extract "HI" and name the key 'HI', leave "bug" as is
3. click on the 'HI' key in the properties file
==> it jumps to the constant reference in println(HI);

Comment 1 Eclipse Genie

2019-06-12 00:58:57 EDT

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.

Comment 2 Dani Megert

2019-06-12 05:13:34 EDT

Still reproducible using 4.12 RC2.

Comment 3 Eclipse Genie

2021-06-02 10:53:31 EDT

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.

Comment 4 Eclipse Genie

2023-06-17 15:43:01 EDT

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.