Good point. It makes sense to only exclude deprecated API.
I needed to find a workaround for the Scala API. The japicmp plugin seems
to have an issue with Scala's @deprecated annotation. But excluding all
*scala files (considering that we want to remove all these classes, anyway)
should be a good
Hi Matthias,
I'm not an expert in japicmp. Is it possible to only disable this for
deprecated APIs? Maybe add an exclusion for @Deprecated? I think that would
reduce the risk of unintended breaking changes to deprecated APIs that are
not yet ready for removal.
Best,
Xintong
On Thu, Aug 29, 20
Hi Matthias,
I would turn japicmp for 2.0 off because adding a long list of exceptions
doesn't give any value.
1.x and 2.x is not going to be compatible in any way and when 2.x released,
then that will be the new
japicmp baseline (after a heavy migration).
What I see as a potential risk it that w
