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.
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.
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.
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.
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.
This will be implemented in NB6.5 Milestone2. *** This issue has been marked as a duplicate of 79782 ***