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.
I have tried the Eclipse importer, and found that for a two-project import, where C is the main project which uses B which in turn exports a jar A.jar, the classes in A.jar are not available to the java classes in C. We use this a lot as it is an easy way to package libraries with source without needing to recompile, so this is a show stopper for using netbeans as a supplement to Eclipse. I have included a workspace showing the behaviour (which also includes _project_ A used to generate the a.jar file in project B).
Created attachment 31654 [details] three project workspace. In Netbeans import C (and B) but not A.
Simple solutions: as a workaround (solution?) you may add 'a.jar' to the run-time classpath of the C project (C's project properties -> Libraries -> Run). Than you may run the C project without problem from NetBeans. Also in C project's root directory create empty manifest.mf - this will allow appropriate distribution generation (this is little odd but it is done by NetBeans j2se project generator automatically and I will also do so in the next version of the Eclipse Importer). I don't know how you create final distribution in Eclipse - I do not know too much about this facility in Eclipse (if there is some) Clear solution would probably be to check such dependencies and add them to the run-time classpath of an imported NetBeans projects appropriately/automatically. Eclipse projects have probably a little different semantics for classpath handling. But imported projects should definitely works as much as similar to a project in Eclipse. Thanks for the attachment which allowed quick reproduction. For me: except setting an appropriate run-time classpath, generate manifest.mf in an imported project's root directory (this will allows clean dist-build - cf. nbbuild/build-impl.xml#-do-jar-with-libraries -> manifest.available+main.class+mkdist.available). Also keep watching similar enhancement in general project infractructure (can't find an issue now) which could possibly solve the same/similar things...
Thank you for your suggestions, but I don't need workarounds (since we just evaluate Netbeans for doing some of the stuff that Eclipse is weak in) but more that the importer works correctly for our eclipse projects. When this bug is fixed in a regular update, I'd be happy to beat some more on this facility.
*** Issue 88668 has been marked as a duplicate of this issue. ***
moving opened issues from TM <= 6.1 to TM=Dev
*** Issue 125869 has been marked as a duplicate of this issue. ***
#d1d111f081a1
Apparently this was for M1.