In the end we need full generic type resolution in order to determine properly whether methods are overridden or not. Right now I can see three possible solutions:

Now that we have shown that ClassMate can solve the issue, we could try to re-implement the functionality
- Pro: We own the code (it's invented here )
- Con: Takes time to write
Include the ClassMate code into our codebase
- Pro: No additional dependencies (something we always tried to avoid), no potential conflicts with apps using their own version of ClassMate (provided we also rename the packages)
- Con: Loosing the ability to easily upgrade/patch, format of code is very different to the HV one (causes problems with ~~HV-640~~), does hide origin of code
Add ClassMate as standard dependency
- Pro: Easy, shows origin of code
- Con: User needs to add another library, potential version conflict

As an alternative to ClassMate we could use gentyref which seems, however, inactive. The share plugin is probably out of question as well. See ~~HV-534~~.

Right now I favor #3

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira