Bug 491071 - [pull up method] A behavior preserving transformation (Pull Up Method Refactoring) is rejected. [Field is referenced in one of the moved elements is not accessible from type ]
Summary: [pull up method] A behavior preserving transformation (Pull Up Method Refacto...
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.5   Edit
Hardware: PC Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-05 07:17 EDT by Melina Mongiovi CLA
Modified: 2022-06-27 06:06 EDT (History)
0 users

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 Melina Mongiovi CLA 2016-04-05 07:17:02 EDT 
Behavior Preserving Transformation is rejected.

Reproducible: Always

Steps to Reproduce:
1. Create the following classes

public class A {
  int x;
}

public class B {
  int x;
  void m() {
    x++:
  }
}




2. Apply the pull up method refactoring to move method m() from class B to class A.

3. The tool does not apply the transformation and warn the following message:
Field 'B.x' referenced in one of the moved elements is not accessible from type 'A'.

4. However, the following possible resulting program compiles and the transformation preserves the program behavior, which indicates that some refactoring conditions may be overly strong. 

public class A {
  int x;
  void m() {
    x++:
  }
}

public class B {
  int x;
}
Comment 1 Eclipse Genie CLA 2020-07-04 02:50:50 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 2022-06-27 06:06:55 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.