Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 430240

Summary: [clean up] Java save actions static class qualifier access same name
Product: [Eclipse Project] JDT Reporter: Marco Janc <marcojanc>
Component: UIAssignee: JDT-UI-Inbox <jdt-ui-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: noopur_gupta, srikanth_sankaran
Version: 3.8.1   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard: stalebug

Description Marco Janc CLA 2014-03-12 23:32:26 EDT
Java Formatter/Save-Actions

Activating static class qualifier access in save-actions or code-formatter results in bug if there is a variable who's name equals the class name itself.

Settings:

"Member Access"->"Static accesses"->"Use declaring class as qualifier"


Solution:

Do not use class qualifier if there is variable with name equal to class name itself.


Example:


class Test
{
    public static final int Test = 0;
    public static final int VALUE = 1;

    void method()
    {
        int x = Test.VALUE;
    }
}

"int x = Test.VALUE;" Value cannot be resolved, 
but using just "int x = VALUE;" works in this case
Comment 1 Srikanth Sankaran CLA 2014-09-10 22:16:22 EDT
Pass to UI for comment.
Comment 2 Eclipse Genie CLA 2020-05-18 16:46:29 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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 3 Eclipse Genie CLA 2020-05-18 16:46:29 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.