Details
-
Type:
Bug
-
Status:
In Progress
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
(from mailing list)
—
Looks like type variable name aliasing can cause incorrect type resolution.
Ok, I can see why this occurs. But while it would be relatively easy to solve this particular case by changing ordering of bindings, this would result in another test failing – may need to see if this is enough to go check out how Jackson 2.0 could just use java-classmate resolver to fully address flaws in current resolution scheme.