Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 316831 - [pull up] pulling up a method changes a method call due to visibility
Summary: [pull up] pulling up a method changes a method call due to visibility
Status: CLOSED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-14 17:08 EDT by Gustavo Soares CLA
Modified: 2020-05-17 17:11 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gustavo Soares CLA 2010-06-14 17:08:55 EDT
Build Identifier: 20090920-1017

Apply the pull up method to a method leads to a behavioral change. After the refactoring, a method call refers to a private method.

Reproducible: Always

Steps to Reproduce:
1. Create the classes:

public class A  {
  private int k() {
    return 20; 
  }   
}
public class B extends A {    
  public int k() {
    return 10; 
  }
  public int m() {
    return k();
  }   
  public int test() {
    return m();
  }
}

2. the method test returns 10
3. Apply the pull up method to m():

public class A  {
  private int k() {
    return 20; 
  }
  public int m() {
    return k();
  }       
}
public class B extends A {    
  public int k() {
    return 10; 
  }
  public int test() {
    return m();
  }
}

4. After the refactoring, the method test returns 20.
Comment 1 Eclipse Genie CLA 2020-05-17 17:11:08 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.