You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Andrew Onischuk (JIRA)" <ji...@apache.org> on 2015/10/13 16:55:05 UTC
[jira] [Resolved] (AMBARI-13403) Ambari unable to build rpms with 4
digit versions
[ https://issues.apache.org/jira/browse/AMBARI-13403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Onischuk resolved AMBARI-13403.
--------------------------------------
Resolution: Fixed
Committed to trunk and branch-2.1 and branch-2.1.2
> Ambari unable to build rpms with 4 digit versions
> -------------------------------------------------
>
> Key: AMBARI-13403
> URL: https://issues.apache.org/jira/browse/AMBARI-13403
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 2.1.3
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)