Bug 199033

Summary:	Rename package should show warning directly in dialog
Product:	[Eclipse Project] JDT	Reporter:	Dani Megert <daniel_megert>
Component:	UI	Assignee:	Markus Keller <markus.kell.r>
Status:	NEW ---	QA Contact:
Severity:	minor
Priority:	P3	CC:	benno.baumgartner
Version:	3.3
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Dani Megert

2007-08-07 05:25:14 EDT

I20070807-0010.

Have:
pack
pack.sub

When I rename pack into pack.sub including sub-packages and click OK I get a warning dialog, however, when I uncheck rename of sub-packages the error is directly shown in the dialog. The same should happen for the warning.

This should be a general rule for cheap tests.

Comment 1 Benno Baumgartner

2007-08-07 07:00:04 EDT

Choosing 'pack.sub' is an error if you do not rename subpackages. The error has to be shown on the dialog and 'ok' needs to be disabled.
If you do rename subpackages you can execute the refactoring, and get a warning while doing so. The refactoring may also produce other warnings... As far as I know all our refactorings work like this.

Markus, decide if you want to show the warning on the dialog already. It would certainly be a usability improvement.

Comment 2 Eclipse Genie

2020-09-04 12:08:44 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 3 Eclipse Genie

2022-10-06 20:06:00 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.