Bugzilla – Full Text Bug Listing
| Summary: | importing plugins resulted in 9MB of errors added to log | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Adam Kiezun <akiezun> |
| Component: | Core | Assignee: | Philipe Mulet <philippe_mulet> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | dejan |
| Version: | 1.0 | ||
| Target Milestone: | 2.0 F2 | ||
| Hardware: | PC | ||
| OS: | Windows 2000 | ||
| Whiteboard: | |||
|
Description
Adam Kiezun
As you can see from the log, the exceptions are coming from JDT - PDE is just the messanger. BTW, from the path, I can tell you are using an old workspace because PDE does not allow binary projects without copying any more. We made the logging explicit in any case one is asking for the classpath of some project which is existing and opened but for which the .classpath file is missing. I am suspecting PDE did silently remove the file and did not add it back (for some obscure reason?). We are currently investigating what is going on, early suspicion is that listeners of java model events are asking for refreshing while PDE is performing, and are asking questions they should not or which expose the fact that the .classpath file is missing. Clients of JDT/Core are guilty for causing the logging. Removing logging (unless in tracing mode). Note: we are still investigating in parallel to see if PDE import is causing us some grief. Fixed I remember that this problem occured in the past when people did the following: 1) Place the workspace in location A 2) Run the build Bn by pointing to A 3) Import plug-ins from Bn as binary WITHOUT copying (meaning that projects were created as external and .classpath was written directly into eclipse/plugins/..) 4) After a while, when build Bn+1 arrived, they removed Bn and unzipped Bn+1 in the same place. 5) They started Bn+1 by pointing at workspace A. Since projects still point to the same location (Bn+1/eclipse/plugins/) but .classpath files are missing, JDT complains. The solution for this problem was to unzip a new build in a new location and use Bn to import binary projects into workspace A by pointing at Bn+1. This way, new projects are created and .classpath is written into the tree. After this, Bn can be discarded and Bn+1 can be launched. The key is make a transition without starting the workspace A that points to the location now replaced with a new build. The new PDE drivers do not allow binary import without copying, so this is not an issue any more. I have no idea how to verify this. Verified |