Bug 373863 - Refactor move project files without dependencies on a package to a more abstract project
Summary: Refactor move project files without dependencies on a package to a more abstr...
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.8   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-10 09:10 EST by Glenview Jeff CLA
Modified: 2012-03-10 09:10 EST (History)
0 users

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 Glenview Jeff CLA 2012-03-10 09:10:12 EST 
Build Identifier: 20110916-0149

I have two Eclipse projects: one that depends upon a certain library (android.jar) and one that is more abstract and doesn't contain that dependency.

I am in the process of migrating all classes that have no dependencies on the package, in my case android.*, to the more abstract project. 

There should be an Eclipse feature that can help automate the move.

Ideally, there would be feature that directly lets you automatically search for and move files that can be safely relocated to a new project.  It would move files that are:

    independent of a specified package (with wildcards)
    independent of other files within the same project that are dependent on the same package (in other words, no indirect dependencies on the package)

I know I could use an external search tool at like the following to at least find files without direct references to a given external package, but this can't meet the second criterion specified above.

grep -r -L "import android\." --include='*.java' .



Reproducible: Always