Community
Participate
Working Groups
I don't know if this is a PDE problem; I had trouble finding a matching component. Please reassign as needed. The error in the summary appears (for the first time) in RC1, even though the org.eclipse.core.boot is imported and appears as a project in my workspace. If I remove the dependency, I can't reset it; org.eclipse.core.boot doesn't appear in the Add dialog list.
Could you describe more precisely where the error is appearing and how to reproduce it?
In the project Properties > Java Build Path. What I saw: Project checked out from CVS into RC1; last built in 3.0.1. Build Path had an explicit dependency on org.eclipse.core.boot, which produced the Error message in the summary. Removing the org.eclipse.core.boot dependency made the error go away, but it was not possible to put it back. Clicking the Add button produces a dialog that does not include org.eclipse.core.boot. Why I see this and you may not: I have a number of Java projects that are built into jar files and incorporated with my plug-in at run time. So they appear in the plugin.xml as required internal jars. However, it is very inconvenient to develop if I have to build a jar file every time I make a change in one of these projects. So I forego PDE's "help" in setting up the build dependencies from the manifest and instead explicitly specify them in the Build Path.
Not a PDE issue. The user is manually managing his .classpath file.
Is this still an open issue? Closing as REMIND. Pleas reopen if 3.2.1 or 3.3 builds still have the problem.
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.
