Bug 461326 - [refactoring] Moving a package-private class to another package does not prompt to make it public
Summary: [refactoring] Moving a package-private class to another package does not prom...
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.4.1   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-03 12:10 EST by Zorzella Mising name CLA
Modified: 2022-08-19 00:06 EDT (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 Zorzella Mising name CLA 2015-03-03 12:10:05 EST 
If you have a package-private class and move it to another package, it always breaks any usages of that class, because Eclipse does not prompt to make the class public. Say:

*********

package foo;

class ToMove {}

*********

package foo;

class WillBeBrokenByMove {
  ToMove toMove = new ToMove();
}

*********

And then move "ToMove" to any other package.
Comment 1 Eclipse Genie CLA 2020-06-12 15:25:19 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-08-19 00:06:47 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.