Wrong constraint validator type resolution in case of constraint placed on parameterized type in class hierachy

Description

there is a difference in the processing of raw type and <?> type.
here is my use case :

With:

everything works fine, though when:

I get the following exception :

workaround :

  • do not use @Inherited annotation

  • use @SuppressWarnings("rawtypes") instead of inferring <?>

Environment

None

Assignee

Hardy Ferentschik

Reporter

Mathieu Lachance

Labels

None

Feedback Requested

None

Feedback Requested By

None

backPortable

None

Suitable for new contributors

Yes, likely

Pull Request

None

backportDecision

None

backportReEvaluate

None

Components

Fix versions

Affects versions

Priority

Major
Configure