[
https://issues.apache.org/jira/browse/AMBARI-11564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566836#comment-14566836
]
Hudson commented on AMBARI-11564:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #2767 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2767/])
AMBARI-11564: Ambari Admin View version is hardcoded in view.xml (jluniya)
(jluniya:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=3ac16966d577f8d956ef3b1189fb4d97a55e3f79)
* ambari-admin/set-ambari-version.cmd
* ambari-admin/pom.xml
* ambari-admin/set-ambari-version.ps1
* ambari-admin/set-ambari-version.sh
> Ambari Admin View version is hardcoded in view.xml
> --------------------------------------------------
>
> Key: AMBARI-11564
> URL: https://issues.apache.org/jira/browse/AMBARI-11564
> Project: Ambari
> Issue Type: Bug
> Components: ambari-admin
> Affects Versions: 2.1.0
> Reporter: Jayush Luniya
> Assignee: Jayush Luniya
> Fix For: 2.1.0
>
>
> Ambari Admin View version is hardcoded to 2.1.0.0. However, the logic in
> Ambari Web was changed to assume the Ambari Admin View is same as Ambari
> version (refer: AMBARI-10533). We need to update the ambari admin build
> process to dynamic set the version in view.xml
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
