Summary: | Exception Thrown While Processing Active Annotation | ||||||
---|---|---|---|---|---|---|---|
Product: | [Tools] AspectJ | Reporter: | Dan Repik <danrepik> | ||||
Component: | Compiler | Assignee: | aspectj inbox <aspectj-inbox> | ||||
Status: | NEW --- | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | CC: | aclement | ||||
Version: | 1.8.3 | ||||||
Target Milestone: | --- | ||||||
Hardware: | PC | ||||||
OS: | Windows 7 | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Dan Repik
2014-08-30 07:53:22 EDT
I have managed to recreate an illegalstateexception - but intermittently. Below the IllegalStateException it should show the original root cause. In both situations I could recreate it was a ZipException, one was: java.util.zip.ZipException: invalid code lengths set and the other was java.util.zip.ZipException: invalid LOC header Both of these seem to me like they are related to reading/writing the jar file in the same eclipse in some way but I can't quite pin it down yet. I'd suspected it was somebody not correctly closing the jar and it being updated whilst still open but a cursory check in the code seems to show it being closed correctly. Once I got into this situation I could just restart eclipse and it worked fine until I started updating the jar again by re-exporting the processor. I am on mac which I know is more lenient on zip file locks compared to windows, I should perhaps try this on windows too. One note, you've updated the processor SupportedAnnotationTypes but haven't changed the reference to SuppressWarnings inside the process() method - both will need updating. Thanks for testing this functionality! |