| Summary: | Corrupt bundle jar not detected | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | Dean Roberts <dean.t.roberts> | ||||||||
| Component: | p2 | Assignee: | P2 Inbox <equinox.p2-inbox> | ||||||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||||||
| Severity: | major | ||||||||||
| Priority: | P3 | CC: | matthew, ob1.eclipse, pascal, pwebster, remy.suen, tjwatson | ||||||||
| Version: | 4.0 | ||||||||||
| Target Milestone: | --- | ||||||||||
| Hardware: | PC | ||||||||||
| OS: | Windows 7 | ||||||||||
| Whiteboard: | stalebug | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Dean Roberts
Created attachment 206809 [details]
Bad jar file (64 bit windows)
Created attachment 206810 [details]
Stack Trace
What was the repository the JAR came from? p2 verifies hashes for files when it downloads them if they are defined. I ran with the bad jar file with the following property set: osgi.signedcontent.support=runtime Startup still looked clean. Upon invoking code assist I get a NoClassDefFoundError instead of the ClassFormatError Created attachment 206811 [details]
Stack Trace with osgi.signedcontent.support=runtime set
(In reply to comment #3) > What was the repository the JAR came from? > > p2 verifies hashes for files when it downloads them if they are defined. The update came from http://download.eclipse.org/eclipse/updates/4.2-I-builds (In reply to comment #4) > I ran with the bad jar file with the following property set: > > osgi.signedcontent.support=runtime > > Startup still looked clean. Upon invoking code assist I get a > NoClassDefFoundError instead of the ClassFormatError That is less than fortunate. I opened bug 363528 to try and improve that error condition. After talking to Dean it is unclear if this error occurred immediately after an update, or at a later point in time. Most likely it was later since the error happens (with a modal dialog) whenever code assist tries to run and he has "auto code assist" enabled in his workspace. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |