Summary: | IOException when searching for packages | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Dani Megert <daniel_megert> |
Component: | Core | Assignee: | Jerome Lanneluc <jerome_lanneluc> |
Status: | RESOLVED WORKSFORME | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 2.0 | ||
Target Milestone: | 2.0 F3 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Dani Megert
2002-06-05 05:30:04 EDT
Dani, which VM are you using to run Eclipse? It happened when using J9. Please annotate this PR if you can reproduce. I alreaday state that I can't but thought you might see something in your code where you missed a guard. The problem is that the error is probably caused by a corrupt (don't know why) Java Model. You can close the bug. I'll file a new one if I see it again. The problem is that the worksapce will not help you since it did not appear again after restarting. Ok this could be a bug in the JCL if it occurs only on J9 and not on any other VMs. Closing as J9/JCL bug. It seems fairly clear from the traceback that the issue is a zip file that J9 has determined is 'invalid'. Unfortunately, there isn't enough information in this PR to determine which zip file this is. Is there any way someone can track down which zip file? Claiming this is a J9/JCL bug is fine -- but without further information, it is basically impossible to track the bug down. I could not reproduce in the workspace after restarting. My guess would be that it came from a corrupt Java Model. I would not conclude that this is a J9 bug. Just curious: what makes you think that the Java Model is corrupt? 1. It happened during a Java search (I searched for a package fragment root) 2. Exiting and restarting made the problem go away (no change in the resources itself) I still don't understand: what I see is that the VM/JCL sayed it was an invalid zip file, but this zip file appears to be valid as when you restarted everything was ok. Couldn't the problem be caused because I searched for a folder in a resource project? Maybe this might help: I was playing around with .java files outside the buildpath and I think I added a .java file into that folder. If the .java would be registered in the Java Model (e.g. because the Java Editor has a working copy in hand) couldnt' then that (resource) folder be some sort of invalid pkgfrmtroot? In this case, we don't create a JarPackageFragmentRoot but a regular PackageFragmentRoot (which doesn't attempt to open a zip file) |