This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 72968 - "extract new project" refactoring
Summary: "extract new project" refactoring
Status: NEW
Alias: None
Product: java
Classification: Unclassified
Component: Project (show other bugs)
Version: 5.x
Hardware: Macintosh All
: P3 blocker (vote)
Assignee: Tomas Zezula
Depends on:
Reported: 2006-02-23 14:49 UTC by jportway
Modified: 2011-08-31 14:06 UTC (History)
0 users

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description jportway 2006-02-23 14:49:41 UTC
The most useful refactoring for me would be the ability to select some classes (or packages) and extract 
them into a new "Java Library" project, making the original project depend on the new project and 
managing any library dependencies etc. In an idea world there would be a really sophisticated version 
of this that could analyse dependencies within a project and suggest ways to refactor the project into 

For instance, up to now I've been building the client and server for my application within the same 
project (the client code has primarily been used to test the server functionality up to now), but now I 
want to move the client into a project of it's own to clean up the server build. Both the client and the 
server rely on some common network code though, so I'd like a refactoring that would analyse the 
dependencies and automatically create a shared "networking" sub-project, and the new "client" project, 
and set up the dependencies between them. Obviously this couldn't be completely automated and 
would probably need a fairly sophisticated interface to allow you to juggle dependencies around (for 
instance there might be some network code that was only currently used by the server, and which the 
client code had no dependency on, but that really belongs in the network sub-project anyway - I should 
be able to manually add those classes to the sub-project).

This is probably very ambitious, but I think it would rove to be extremely valuable.
Comment 1 Jan Pokorsky 2008-10-16 15:04:23 UTC
Reassigning to java projects for evaluation since the requested functionality relates rather to java project support. In
order to manipulate with java classes you can reuse existing java refactorings.