Summary: | [generics] field-get problems when generic field is used. | ||
---|---|---|---|
Product: | [Tools] AspectJ | Reporter: | Misha Kantarovich <michaelk> |
Component: | Compiler | Assignee: | Adrian Colyer <adrian.colyer> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | critical | ||
Priority: | P3 | ||
Version: | 1.5.0M4 | ||
Target Milestone: | 1.5.0RC1 | ||
Hardware: | PC | ||
OS: | Linux | ||
Whiteboard: |
Description
Misha Kantarovich
2005-10-26 14:01:17 EDT
Doesnt look like you are doing anything wrong. And I am not surprised it worked in M2 and fails now, M2 was not generics aware and it would have been working 'by accident'. Now the whole compiler/weaver is much more aware of generics and this kind of thing is going to happen whilst we get it right. I can see why this is failing, fix almost ready. Fix checked in, waiting on build before closing. As suspected it was that the system was more generics aware ... apart from in one place ;) (In reply to comment #3) > Fix checked in, waiting on build before closing. As suspected it was that the > system was more generics aware ... apart from in one place ;) Thanks! I'll download the build as soon as it will be there ... fix available in the latest dev build from the AJ download page. |