-
Task
-
Resolution: Unresolved
-
Neutral
-
None
-
None
-
-
Empty show more show less
-
Empty show more show less
Since the switch to permanent SNAPSHOTs, running japicmp locally is inconvenient, because the current version of the module (6.2-SNAPSHOT) is not correct when it comes to comparing for instance 6.2.16 to 6.2.17-SNAPSHOT.
While that isn't a blocker, try to resolve by introducing a PPOM profile. The goal is to automatically resolve the last version that was released, and to somehow interpolate it with the current version. A couple of approaches could be attempted:
- using the versions plugin to resolve the next version?
- https://www.mojohaus.org/buildnumber-maven-plugin/usage.html
- replicating the approach currently being implemented for pipeline-templates where the list of Git tags is inspected
- is related to
-
MAGNOLIA-8298 Adapt Magnolia's versioning schemes (X.Y versions) for permanent SNAPSHOTs
- Closed
-
BUILD-680 Run japicmp correctly with permanent SNAPSHOTs (in pipelines)
- Closed
-
BUILD-756 Local development profile that replicates Jenkins CI behavior
- Closed