[BUILD-418] japicmp won't parse Magnolia major releases (X.Y) pattern Created: 19/Nov/20  Updated: 08/Apr/21  Resolved: 31/Mar/21

Status: Closed
Project: Build
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Maxime Michel Assignee: Maxime Michel
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to BUILD-407 Improve API compatibility reports Closed
is related to BUILD-445 japicmp works with standard SemVer, b... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty

 Description   
  • either adapt the regular expression in poms/base/pom.xml
  • or make new majors use the X.Y.Z pattern

Indirectly related to this issue is also the question of the first version. When a new module is created, we have to bypass the check, because it's going to fail because it can't find a previous version. So that must be either 1.0-SNAPSHOT, or 1.0.0-SNAPSHOT if we go for a new convention.



 Comments   
Comment by Maxime Michel [ 31/Mar/21 ]

This can't be solved by a regular expression. It's easy enough to write one that matches X.Y and X.Y.Z: <oldVersionPattern>\d+\.\d+(\.\d)?</oldVersionPattern>

But that's not telling japicmp which to prefer. In practice, it still favors SSO 1.0.3 when asked to analyse 1.1.1-SNAPSHOT using that pattern.

Generated at Sun Feb 11 23:41:44 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.