[
https://issues.apache.org/jira/browse/HBASE-8275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13623303#comment-13623303
]
Lars Hofhansl commented on HBASE-8275:
--------------------------------------
I would envision the following.
# Find all classes annotated with InterfaceAudience=Public.
# In those classes find all public methods
# Check those names against a gold file
# If the new files does not match, overwrite the gold file (so that it can be
easily checked in)
So the file to be checked in is automatically generated and we won't forget to
add new methods or classes (as long as the classes are annotated correctly)
> 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
