Description
Happens in 1.0.0 and in 1.1.0-SNAPSHOT.
If you use a portable Extension which provides information via @Observes ProcessAnnotatedType pat ... pat.setAnnotatedType(WrappedAnnotatedType..)
then any available @Typed annotation on the class will not be used to determine the typeClosured hierarchy. Instead of using solely the information of the @Typed annotation, we currently always parse the Class hierarchy.
This leads to AmbigiousResolutionExceptions in some cases.