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 139183

Summary: Reference tree for compiler dependencies
Product: java Reporter: janicki <janicki>
Component: CompilerAssignee: Dusan Balek <dbalek>
Status: NEW ---    
Severity: blocker    
Priority: P4    
Version: 6.x   
Hardware: All   
OS: All   
Issue Type: ENHANCEMENT Exception Reporter:

Description janicki 2008-07-07 22:56:56 UTC
I have a large project (1000+ *.java files).  It is a client/server design with a full-fledged client application.  Somehow, there are references being made to 
server-side classes that drag in the entire server code in when compiling just the client.  This makes for an extra-fat client.  I am finding it very difficult to 
figure out where the critical link is occurring.  

I've created my own GUI utility that tries to draw the output of 'javac -verbose' as a tree, to trace which java source files preceeded the loading of others.  
This helps narrow things somewhat.  But I am hopeful there is a NetBeans engineer more familiar with the workings of the compiler that might have a 
better solution.  (I can post my utility if that would be of any help.)

Ideally, I would like to enter the name of a class or package that should not be included in the build, then have the NetBeans feature tell me how the class 
or package got dragged into the compilation.

I think this feature might be useful for other people too.  For example, I sometimes don't know why I must include some jars in my deployment... it would 
be nice to know exactly where the jars are required.  (Deleting the jar may cause a useful ClassNotFoundException at runtime, but maybe not right away, 
and it will only reveal the first place the jar is referenced.)