Bug 314887 - Check for corrupted jar files when adding them to the classpath
Summary: Check for corrupted jar files when adding them to the classpath
Status: CLOSED DUPLICATE of bug 229038
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.5   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-28 10:55 EDT by Luciana Moreira CLA
Modified: 2010-05-28 12:26 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Luciana Moreira CLA 2010-05-28 10:55:24 EDT
Build Identifier: 20090621-0832

After adding many jar files to the project classpath I got an error in the Java editor every time that I tried to press F3 to open a class, even though the project apparently had no errors.

It turns out that a license.txt was also added together with the jar files to the classpath. Eclipse did not show an error on the build classpath screen nor when I pressed F3. It would be useful if Eclipse could verify if the jar/zip files are:
1) Not corrupt
2) Are indeed a jar file

Reproducible: Always

Steps to Reproduce:
1.Add a .txt file as a jar in the classfile
2.Try to open a class with F3
Comment 1 Markus Keller CLA 2010-05-28 12:26:47 EDT

*** This bug has been marked as a duplicate of bug 229038 ***