Community
Participate
Working Groups
i20030826 This seems like a regression of bug 38291. See that bug for a test case.
Using the 3.0M3 warm-up build, I tried the scenario in bug 38291 with three different types of import: binary, binary with links, and source. Could not reproduce the problem. However, I'll keep open for further investigation. By the way, did you try to explicitly update the project's classpath after that? This must have worked.
I could reproduce it with a new workspace. Steps: 1) File->Import...->External Plug-ins and Fragments 2) Kept all default options 3) Selected all plug-ins (Add all) and pressed Finish 4) All plug-ins were properly imported, but no .classpath files were created. The following problem appears for every imported plug-in: "The project cannot be built until build path errors are resolved." And yes, your workaround works (update all classpaths and rebuild all).
the import operation is two stages, and you might see transient markers between the first and second stage, but they do go away at the end of the operation. Out of curiosity, what VM are you using?
I forgot one important detail in my configuration (sorry about that)... I was using background auto-builds. Now, if I turn back-ground auto build off (through the debug options file), everything goes fine. Reduced severity since this is not going to happen in the normal case (background auto-builsd are off by default) http://dev.eclipse.org/mhonarc/lists/eclipse-dev/msg03772.html Adding John for comments.
*** Bug 41762 has been marked as a duplicate of this bug. ***
I have also encountered this bug. My basic configuration is RH Linux 9, IBMJava2-141, Eclipse 3.0 M3. The problem was corrected by reverting to the 1.3.1 JDK level. (IBMJava2-1.3.1- 5.0). In my case (with Java 1.4.1): a) Binary projects imported included org.eclipse.core.resources.linux and required plugins (totaling 5) b) project .classpath files were not generated on import or afterwards. c) Update Classpaths... did not work because _the Update Java class path dialog showing "Available plug-ins and fragments" was empty (legend at bottom was "0 of 0 selected"_. In other words, Update Classpaths... thought there were no Java projects in the workspace even though 5 binary projects had been imported. (BTW, I have also noticed fairly flaky JDT editor behavior on Windows, using IBM Java 1.4.1: The code formatter suddenly stops working, and Eclipse must be restarted to correct this. I will now try using M3 with Java 1.3.1 on Windows, to see if that corrects the problem. Perhaps Java 1.4 is not fully compatible with Eclipse?)
Fixed in M4.
