japicmp: Build fails if new artifact removes a class even with major version change
I’m using <breakBuildBasedOnSemanticVersioning>true</breakBuildBasedOnSemanticVersioning> to enforce proper semantic versioning in my maven builds.
I think removing a class is allowed if I bump the major version, but the plugin fails the build, and suggests I add --ignore-missing-classes.
About this issue
- Original URL
- State: open
- Created 7 years ago
- Comments: 16 (8 by maintainers)
@siom79: I am seeing this problem too. I’m not sure I understand, is this behaviour by design? Why is a missing class not just marked as an incompatibility instead of an error?