Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Tue, 13 Oct 2015 14:55:05 +0000 (UTC)
From: "Andrew Onischuk (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12904565.1444747372000.24830.1444748105144@Atlassian.JIRA>
In-Reply-To: <JIRA.12904565.1444747372000@Atlassian.JIRA>
References: <JIRA.12904565.1444747372000@Atlassian.JIRA>
 <JIRA.12904565.1444747372006@arcas>
Subject: [jira] [Resolved] (AMBARI-13403) Ambari unable to build rpms with 4
 digit versions
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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)