Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
We tried making the change but the rpms being created do not get the correct version number.
The goal is to create a build with version 2.1.2.0.378. As you can see the rpms being created are with version 2.1.2-0:
... ambari-metrics-monitor/RPMS/x86_64/ambari-metrics-monitor-2.1.2-0.x86_64.rpm
It seems as if the build is not processing a 4 digit version + build properly. DnewVersion=2.1.2.0.378 is being broken such that the 4th digit is becoming the build number. I suspect the replacement directive in POM needs to be changed.
Attachments
Issue Links
- links to