Community
Participate
Working Groups
build 20020123 I have a workspace with a project org.eclipse.jdt.ui defined by the PDE selfhosting plugin. After I used the import feature of that plugin to create a selfhosting workspace I had an error "The project was not built since it is inconsistent. Refresh this project then rebuild it". When I refresh the project and rebuild I get another error with the same message. The errors don't go away. Before I added the org.eclipse.jdt.ui project I deleted a manually imported one of the same name. I'm pretty sure I selected to delete the contents from disk as well but it was still there when I checked after getting the above error message. Note that the deleted files were in my workspace directory whereas the PDE selfhosting import creates a project residing in the plugin directory. It doesn't create it in the workspace directory. That is why the refresh from local did not add the stale files from my workspace directory. Perhaps the builder got confused by the change in project location? I'm uploading my workspace to walleye as va2000/INCOMING/forKnut/<thisbugnumber>.zip
I think this is related to 8509. When the original project was deleted it wasn't completely removed.
Knut: the zip file on walleye does not include the projects org.eclipse.jdt.ui & org.eclipse.ui. Both projects believe they're in D:\Images\Eclipse\dev\eclipse20020122\plugins
It should be sufficient if you copy the missing projects/plugins from any current drop to the referenced location (D:\Images\Eclipse\dev\eclipse20020122 \plugins). I don't think it matters what code you are working with during the rebuild after refreshing. The duplicate errors probably appear because of some weird workspace state and not because of the actual code that is used by the builder.
All the prereq projects for org.eclipse.jdt.ui & org.eclipse.ui are closed. In the latest build, you will see a warning for each prereq project which is closed. In previous builds, closed projects threw CoreExceptions which were trapped with the generic error message you received. *** This bug has been marked as a duplicate of 8340 ***