Hi everyone,
for the 2.0 work, we are expecting to run into public API changes quite a
bit. This would get picked up by the japicmp plugin. The usual way is to
add exclusions to the plugin configuration [1] generating a (presumably
long) list of API changes.

I'm wondering whether we, instead, would want to disable the plugin [2] for
2.0 entirely to lower effort on the contributors side.

Best,
Matthias

[1] https://github.com/apache/flink/blob/master/pom.xml#L2367
[2] https://github.com/apache/flink/blob/master/pom.xml#L170

Reply via email to