Bug 435618 - [nls tooling] Ctrl + Click on plugin.properties search result is not correct
Summary: [nls tooling] Ctrl + Click on plugin.properties search result is not correct
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 4.4   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-23 06:28 EDT by Sarika Sinha CLA
Modified: 2023-01-09 15:49 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sarika Sinha CLA 2014-05-23 06:28:24 EDT 
Ctrl + Click on plugin.properties should search only in plugin.xml file and for the plugin property names with the percent sign (%). Right now it searches in java files and in plugin.xml with/without percent sign(%).
E.g. 
ctrl + click on vmInstallTypePage in plugin.properties of /org.eclipse.jdt.debug.ui

It shows 2 results :
1. 8 results in plugin.xml
2. 1 result in IJavaDebugUICOnstants.java

It should have shown only 1 result in plugin.xml :
name="%vmInstallTypePage"
Comment 1 Eclipse Genie CLA 2020-10-17 18:49:36 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 Eclipse Genie CLA 2023-01-09 15:49:02 EST 
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.