Guidance or Ideas on support ignoring certain classes of changes

[kbendick]

What happened?

Feature request / tool usage assistance!

What did you want to happen?

The Revapi project defines a way to ignore certain types of changes, for example, adding a method to an interface is called out in the docs (though that way of using the maven plugin is apparently deprecated but the idea remains the same)

We’ve begun using gradle-revapi in the Apache Iceberg project, and we’d very much like to suppress BREAKS for “method added to interface”, as the way we use the project / perform releases, we don’t generally expect it to be a problem.

Is it possible to ignore certain types of “breaking” changes now with the existing gradle revapi package? I didn’t see anything, so this is partially a feature request.

I’m somewhat new to revapi myself so it’s possible this is already achievable and I just don’t have my configuration files correctly. But this does appear to be possible with the maven revapi plugin.

Thank you for this wonderful plug-in!

[kbendick]

For reference, this is our .revapi file in the Apache Iceberg project https://github.com/apache/iceberg/blob/master/.palantir/revapi.yml.

The plug-in is applied to one sub module iceberg-api, in our build.gradle file with everything very standard / common setup.

[kbendick]

I'd be open to try helping with this PR if possible (to add a whitelist / ignore list to the revapi file configuration for certain classes).

Please let me know if that's something you'd be open to or not or if hopefully it's already possible 👍