[
https://issues.apache.org/jira/browse/HADOOP-7035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988305#action_12988305
]
Todd Lipcon commented on HADOOP-7035:
-------------------------------------
Tom, this is really cool stuff!
I noticed it classifies a few changes as "incompatible" which I'd have thought
are compatible:
- protected -> public accessibility
- adding an interface to a public class
Am I missing something?
Would it be possible to also distinguish between "source-compatible" and
"binary-compatible" somehow? Some changes (like changing a parameter to a
superclass of the old type) won't work without a recompile of the caller, but
don't require any code change. Whereas others (like changing a parameter to an
entirely unrelated type) obviously do.
Of course these are suggestions for improvements - as is it's already really
useful.
> Document incompatible API changes between releases
> --------------------------------------------------
>
> Key: HADOOP-7035
> URL: https://issues.apache.org/jira/browse/HADOOP-7035
> Project: Hadoop Common
> Issue Type: Improvement
> Components: documentation
> Reporter: Tom White
> Attachments: jdiff-with-previous-release.sh,
> jdiff-with-previous-release.sh
>
>
> We can use JDiff to generate a list of incompatible changes for each release.
> See
> https://issues.apache.org/jira/browse/HADOOP-6668?focusedCommentId=12860017&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12860017
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
