[
https://issues.apache.org/jira/browse/HBASE-8275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13623132#comment-13623132
]
Jean-Marc Spaggiari commented on HBASE-8275:
--------------------------------------------
I prefer Lars' option. Not sure we should rely on an external
application/client/framework to validate.
What with the new added methods? Should we add than in the gold file too to
make sure they are checked in the next release?
At the end, we need to test that release n+1 is still provinding at least the
same methods as release n.
> Tool to test binary compatibility
> ---------------------------------
>
> Key: HBASE-8275
> URL: https://issues.apache.org/jira/browse/HBASE-8275
> Project: HBase
> Issue Type: New Feature
> Reporter: Jean-Daniel Cryans
> Fix For: 0.98.0
>
>
> Stack and I were discussing of ways to make binary compatibility easier to
> test than doing it completely by hand.
> One idea would be to have a tool that uses reflection to generate code that
> calls all the public methods from a list of classes. You would then compile
> this code against the current version you are on, then try it out with
> different HBase jars without recompiling.
--
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
