Using @MappedSuperclass as anchor for @TypeDef has been broken by HHH-14499

Description

Skipping MappedSuperclass in AnnotationMetadataSourceProcessorImpl#insertMappedSuperclasses breaks our current method of collecting UserTypes (@TypeDef) via entity scan.
Currently we annotate our UserTypes, which are used for more than one Entity with @TypDef(defaultForType = XXX.class, typeClass = XXXUserType.class) and also add an @MappedSuperclass, although there is no entity that inherits from this class. In this way the UserTypes are selfcontained and are collected by the entity scan. We want to avoid using TypeDef on package level or repeating the same TypeDef on multiple Entity classes.

We are aware that this is not the standard way to collect TypeDefs, but it is very convenient.

Environment

None

Assignee

Unassigned

Reporter

johannes.rost