Details
-
Type:
New Feature
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
Description
The default value for comparisonVersion being {{(,${project.version})}}, we run into the issue that a release of 4.3 was compared against 4.3-beta-1, or N-beta-2 was compared against N-beta-1, for example.
While those reports are valuable, comparing against the latest final artifact seems more valuable to me. (of course, if having both reports is an option, then that'd be fine too).
Of course, I could use the -DcomparisonVersion flag, but that requires maintenance, and remembering which was the latest version, which the default value does well for us, except for the fact it'll take -betas, -alphas and other -pre or -milestone releases into account.