I need your help concerning the convention to adopt about Spring Boot BOM version as what we did is not perfect.

The current Spring Boot BOM project [1] uses as GAV this convention org.jboss.snowdrop:spring-boot-1.4-bom:2 [2] and when it is released for rhoar, then the GAV is turned into org.jboss.snowdrop:spring-boot-1.4-bom:2.0.0.redhat-63

As you can see the version number of the upstream gav is converted into this number - 2.0.0.redhat-63 during the build and follows this convention

"Version of each productized artifact has to be in form of <major>.<minor>.<micro>
If we put 2 as the version, it is treated as <major> and filled with 0.0 to fulfill this requirement.
redhat- suffix is then added to the version as an indicator that the artifact has been built internally
the number at the end is the next consecutive number (redhat-63 means that there were 62 builds before)"

If we have to fix a problem within the current BOM file, we will (with the actual convention) increase the number from 2 to 3 and when released for RHOAR, then the number will become something like org.jboss.snowdrop:spring-boot-1.4-bom:3.0.0.redhat-xx

The end user/customer could be very perturbed about this version change as the GAV number doesn't follow a logic numbering change (e.g : 2.0.0 -> 2.0.1.redhat-xxx, .....) and also because gav doesn't really include the version supported about Spring Boot which is for the branch 1.4 -> 1.4.1

Ideally, the version number of Spring Boot should become our BOM GAV number --> org.jboss.snowdrop:spring-boot-bom:1.4.1 but if we do that then it will be required to increase the micro number to fix issue, patch, ... but our customers will have the impression that we are moving to the next Spring Boot version 1.4.2.

What do you suggest to do to resolve this problem ? Adding a last digit number as proposed by Ladislav -->org.jboss.snowdrop:spring-boot-bom:1.4.0-jbossorgN and increase -jbossorgN when you have to change the BOM for any reason. Is it supported by PROD ?

[1] https://github.com/snowdrop/spring-boot-bom/blob/sb-1.4.x/pom.xml#L26-L29
[2] https://github.com/snowdrop/spring-boot-bom/blob/sb-1.4-2/pom.xml#L26-L28