Github user PramodSSImmaneni commented on the pull request:
https://github.com/apache/incubator-apex-core/pull/187#issuecomment-170121776
I rebased it but I am having some second thoughts about a different
interface based on the japicmp discussion that @chandnisingh sent earlier.
What do you guys think about relaxing the backwards compatibility
restriction in the following way in cases where an "optional" callback needs to
be added. We ensure that an app compiled against an older version still *runs*
by doing runtime checks or with error handling even though the app will *not
compile* against the new version without changes. When we are going to a new
major version then we can remove those runtime checks.
This may be a scenario we might see a few times in future and using a
different interface each time might just make this a little problematic. I was
planning to look at this over the weekend and in course see if I would need to
implement a small utility for the runtime checks that can be reused in the
future.
Let me know if you think we should be having an email discussion on
apex-dev about this rather than this JIRA.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
