Community
Participate
Working Groups
Eclipse 20021001 Platform Windows 2000 1/ New install 2/ Import external plugins and fragments, binary 3/ Select all org.eclipse.ui.* components 4/ Click on Add Required plugins 5/ import 6/ Open CVS Repository view, select modules 7/ import platform-ui Note the compile errors, the components being complained about are present. This methodology worked prior to the UI reorganization.
The problem you encountered is not a result of a PDE bug. However, you could have used PDE's 'Update Classpath' function to fix the problem. Before you checked out the org.eclipse.ui.* projects from CVS, the exising ones that you imported using PDE's import were binary and had references to .jar files. Then, you checked out multiple cross-referencing projects from CVS without deleting the binary counterparts first. Upon check out, the multiple projects in your workspace are overwritten, not deleted and recreated. The Java Model, as a result, got confused and the errors that you see in the Tasks view are still looking for the jar files which no longer exist after checking out the source projects. You can do one of two things: 1. Delete existing binary projects from your workspace before checking out their source counterparts from CVS, or 2. Do what you did, but use PDE's 'Update Classpath' to fix your problem after the check out is done. The reason why you never ran into the problem before the split of org.eclipse.ui is because you were dealing with one project, as opposed to the current multiple cross-referencing projects. PDE should only be held responsible if the import operation of the binary projects computed the wrong classpath, or if the 'Update Classpath' action resulted in erroneous behavior. Both functions are working properly.
Re-opening, in order to mark it as duplicate of bug 18212
*** This bug has been marked as a duplicate of 18212 ***
