Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 314077 - [move member type] Incorrect message while 'Move Type to New File' when CU not on Build path
Summary: [move member type] Incorrect message while 'Move Type to New File' when CU no...
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.7 M2   Edit
Assignee: Deepak Azad CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 314227
  Show dependency tree
 
Reported: 2010-05-24 05:16 EDT by Deepak Azad CLA
Modified: 2010-09-14 07:28 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Deepak Azad CLA 2010-05-24 05:16:45 EDT
Build I20100520-1744

- New workspace
- Open a Java file placed anywhere on the file system (but is not on build
path)
Use following snippet

package q;
public class B {
    void foo() {
        System.out.println();
    }
}
class A{
	
}
- Select class 'A'
- From the Menu bar 'Refactor' -> Move Type to New File => Dialog saying ' To activate this refactoring, please select the name of a member type or a secondary type' comes up. 

However dialog saying 'the CU is not on the build path' should come up.
Comment 1 Deepak Azad CLA 2010-05-24 05:43:55 EDT
This works when the java file is stored in a simple
project - dialog that 'the CU is not on the build path' shows up.
Comment 2 Deepak Azad CLA 2010-09-08 04:33:53 EDT
Fixed in HEAD in ConvertNestedToTopAction.java
Comment 3 Raksha Vasisht CLA 2010-09-14 07:28:22 EDT
Verified for 3.7 M2 with I20100913-1800.