[
https://issues.apache.org/jira/browse/AMBARI-13403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14955349#comment-14955349
]
Hudson commented on AMBARI-13403:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #3636 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3636/])
AMBARI-13403. Ambari unable to build rpms with 4 digit versions (aonishuk:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c6c7f3955ddae61ac8dadb15dd1503e1e19a5766])
* ambari-metrics/ambari-metrics-flume-sink/pom.xml
* ambari-metrics/ambari-metrics-assembly/pom.xml
* ambari-metrics/ambari-metrics-timelineservice/pom.xml
* ambari-web/pom.xml
* ambari-metrics/ambari-metrics-common/pom.xml
* ambari-client/pom.xml
* ambari-metrics/ambari-metrics-host-monitoring/pom.xml
* ambari-metrics/ambari-metrics-storm-sink/pom.xml
* ambari-project/pom.xml
* ambari-client/groovy-client/pom.xml
* ambari-metrics/ambari-metrics-kafka-sink/pom.xml
* ambari-shell/ambari-python-shell/pom.xml
* pom.xml
* ambari-server/pom.xml
* ambari-client/python-client/pom.xml
* ambari-metrics/ambari-metrics-hadoop-sink/pom.xml
* ambari-shell/pom.xml
* ambari-shell/ambari-groovy-shell/pom.xml
* ambari-admin/pom.xml
* ambari-views/pom.xml
* ambari-metrics/pom.xml
* ambari-agent/pom.xml
* docs/pom.xml
> 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)
