Details
-
Task
-
Resolution: Won't Fix
-
Neutral
-
None
-
None
-
None
-
None
-
-
Empty show more show less
-
Empty show more show less
Description
The SSO 1.1 release lead to the following problem:
- API compatibility got broken when going from 1.0.x to 1.1.x
- which is acceptable in Magnolia SemVer
- however, the check is now running, saying the module should have been bumped to a new major (2.0.x) with such changes
- which is indeed standard SemVer
This ticket is about looking into the following option of the japicmp plugin:
postAnalysisScript true n.a. A Groovy script that gets invoked after analysis is completed and before the output is written. This way it can be used to filter the output or break the build on specific conditions. It can be an absolute path or a relative path of a file within the classpath.
Write a script in order to override the default SemVer validation with Magnolia-specific unwritten rules.
Checklists
Acceptance criteria