| Summary: | org.eclipse.core.runtime.CoreException: I/O exception : Invalid ZIP archive | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Michael Matczynski <mjm> |
| Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | daniel_megert, jarthana, markus.kell.r, Michael_Rennie, Olivier_Thomann |
| Version: | 3.6.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Michael Matczynski
moving to JDT core for comment One of the reasons could be that invalid archive file was added to the project's build path. Can you please check if there are any warnings/errors of an invalid classpath entry? This error was the result of XML and TXT files on the build path. What happened is that I wanted to add all the jars in the axis2/lib directory, and simply selected all the files in the directory (which had XML and TXT files mixed in with JAR files). Seems like the fix is one or both of the following: 1. Java Build Path's "Add JARs..." dialog should filter out all non-JAR files 2. Someone in the callstack should catch the IOException and log/ignore the error. It doesn't make sense to start throwing exceptions in the error log and preventing content assist from working if this is a recoverable error. Thanks! Mike (In reply to comment #3) > Seems like the fix is one or both of the following: > 1. Java Build Path's "Add JARs..." dialog should filter out all non-JAR files This should be done in the UI. Moving to JDT/UI *** This bug has been marked as a duplicate of bug 229042 *** |