Summary: | [generics] UnresolvedType.forSignature throws BCException when using generics | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Tools] AspectJ | Reporter: | Bartek Zdanowski <b.zdanowski> | ||||||
Component: | Compiler | Assignee: | aspectj inbox <aspectj-inbox> | ||||||
Status: | RESOLVED WORKSFORME | QA Contact: | |||||||
Severity: | normal | ||||||||
Priority: | P2 | CC: | aclement, b.zdanowski | ||||||
Version: | unspecified | ||||||||
Target Milestone: | 1.6.1 | ||||||||
Hardware: | PC | ||||||||
OS: | Windows XP | ||||||||
Whiteboard: | |||||||||
Attachments: |
|
Description
Bartek Zdanowski
2007-03-16 10:45:37 EDT
Created attachment 61102 [details]
Original class
Class which aspect applies to
Created attachment 61103 [details]
Aspect file in state when Exception was thrown
Passing over to compiler work into testcase for 1.5.4 and investigate. i tried a quick recreate but can't get it to fail - given the age of the bug (sorry it took me so long to get round to it...) and that the weaver has been largely refactored in the failing area for 1.6.1, I'm not sure it can still fail. The BCException does now include the signature that was causing problems so should it happen again the signature will be included in the stack trace. In fact I half suspect it may be related to the problem of our internal 'P' prefixed signatures leaking out into the .class files - as the forSignature() method that is failing does not cope with 'P' prefixes (and it should not, they shouldn't get passed into here..). So I wouldn't be surprised if the change to fix the problem of leaking P sigs also addressed this situation here. feel free to reopen if anything like this happens again. |