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

Bug 97943

Summary:	[reorg] dragging file back from source folder to original package gives confusing warning [refactoring]
Product:	[Eclipse Project] JDT	Reporter:	Nick Edgar <n.a.edgar>
Component:	UI	Assignee:	JDT-UI-Inbox <jdt-ui-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3
Version:	3.1
Target Milestone:	---
Hardware:	Macintosh
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:	stalebug

Description Nick Edgar

2005-06-01 14:31:39 EDT

3.1 RC1

- org.eclipse.ui loaded from head
- reveal UIPlugin.java
- in Package Explorer, drag UIPlugin.java to src folder
- drag it back to the o.e.ui.internal package
- get a dialog saying (red X) "Found potential matches. Please review changes on the preview page.", 
with no extra pages and a Cancel and a Continue button (both enabled)

Issues:
- Matches to what?  I'm doing a move, not a search.
- There's no preview page.
- Red X indicates an error, not a warning.  If it's really an error, I'd expect Continue to be disabled.

Comment 1 Dirk Baeumer

2005-06-07 07:06:47 EDT

Language wise the problem comes from the fact that we can't import the default
package. Hence the first move results in compile errors.

Regarding the issues:

- we should rephrase this. Move actually searches for all references, but this
  is an implementation detail

- the preview page is missing due to DnD. Fixing this requires larger coding
  which can't be done for 3.1

- since 1.0 refactoring distinguishes between info, warning, error and fatal.
  Users can proceed as long as the status is <= error. We flag something as 
  an error when it is likely that the user ends up having compiler errors
  and as a warning for compile warnings. A fatal is used to signal "can't
  proceed".

Comment 2 Dirk Baeumer

2006-04-05 13:46:40 EDT

Moving due to ownership changes.

Comment 3 Eclipse Genie

2019-12-26 15:31:20 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.

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.