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 125869

Summary: Eclipse Importer Does Not Address Nested Dependencies
Product: projects Reporter: William Leonard <bleonard>
Component: Eclipse project importerAssignee: Jesse Glick <jglick>
Status: RESOLVED DUPLICATE    
Severity: blocker CC: dkonecny, richunger
Priority: P3    
Version: 6.x   
Hardware: All   
OS: All   
Issue Type: DEFECT Exception Reporter:

Description William Leonard 2008-01-23 20:04:25 UTC 
If you import Eclipse ProjC, which depends on ProjB, which depends on ProjA, the Eclipse importer will correctly
identify the dependencies, importing all 3 projects, but not correctly add ProjA to ProjC. Maybe this is really an issue
with the project subsystem, as ideally NetBeans would detect it's dependency on ProjA through its dependency on ProjB
(this is how Eclipse works). Check out this demo for a full description of the problem:
http://wiki.netbeans.org/EclipseWorkspaceImporterDemo.
Comment 1 Rich Unger 2008-03-18 18:00:32 UTC 
Agreed.  I'm in a situation where I have a very complex example of this kind of dependency.  If the importer had even an
option to recursively add the dependencies (i.e. give project A dependencies on External Library, User Library, and
Variable Reference as well as Project C), that would go a long way.
Comment 2 Milan Kubec 2008-03-19 09:52:55 UTC 
This is deficiency of NetBeans project infrastructure that it cannot detect this kind of dependency. Probably not
fixable without major rewrite of project infrastructure.

In importer it might be fixed by explicitly adding all those build artifacts to classpath of the first project.
Comment 3 Rich Unger 2008-03-19 15:42:30 UTC 
Yes, that is what I had in mind.  There could be a checkbox for adding all those build artifacts to classpath of the
first project.
Comment 4 David Konecny 2008-06-16 00:58:57 UTC 
This will be implemented in NB6.5 Milestone2.

*** This issue has been marked as a duplicate of 79782 ***