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

Bug 520776

Summary:	Refactor rename of package with subpackages does not update imports of classes in renamed subpackage -> compile error
Product:	[Eclipse Project] JDT	Reporter:	Julian Ruppel <julian.ruppel>
Component:	Core	Assignee:	JDT-Core-Inbox <jdt-core-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3
Version:	4.7
Target Milestone:	---
Hardware:	PC
OS:	Windows 10
Whiteboard:	stalebug

Description Julian Ruppel

2017-08-09 12:17:24 EDT

Let's assume there are 2 packages
1. org.fo.service
2. org.fo.service.impl

where the first package holds some interfaces and the second package holds the corresponding implementations.

When I refactor rename the first package to org.fo.bar and activate 'rename subpackages' the subpackage gets correctly renamed to org.fo.bar.impl but the classes inside the subpackage can't find their interfaces of the first package since the import statements stayed untouched and are still directing to the old org.fo.service package, which leads to a compile error.

Comment 1 Eclipse Genie

2020-01-23 14:11:59 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. 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.