Unique class name constraint needs to consider type parameters

[Matthias Schoettle]

Given the following two classes, a validation error

The class 'Collection' must be unique

occurs: Class Collection and Implementation Class java.util.Collection<Value>

It appears that type parameters are not considered in order to make sure they are not the same. At the same time, we also might want to allow same names if the other one is an implementation class.