[ https://issues.apache.org/jira/browse/AMBARI-11922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14586974#comment-14586974
]
Hudson commented on AMBARI-11922:
---------------------------------
FAILURE: Integrated in Ambari-branch-2.1 #46 (See [https://builds.apache.org/job/Ambari-branch-2.1/46/])
AMBARI-11922. Adds <build> to each view.xml in contrib (Erik Bergenholtz via rlevas)
(rlevas: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=935b4a66c849dff75928133bcf162fac60a8951b)
* contrib/views/hive/src/main/resources/view.xml
* contrib/views/slider/src/main/resources/view.xml
* contrib/views/jobs/src/main/resources/view.xml
* contrib/views/storm/src/main/resources/view.xml
* contrib/views/pig/src/main/resources/view.xml
* contrib/views/tez/src/main/resources/view.xml
* contrib/views/capacity-scheduler/src/main/resources/view.xml
> Be able to determine which build a particular view comes from
> -------------------------------------------------------------
>
> Key: AMBARI-11922
> URL: https://issues.apache.org/jira/browse/AMBARI-11922
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
> Affects Versions: 2.1.0
> Reporter: Erik Bergenholtz
> Assignee: Erik Bergenholtz
> Fix For: 2.1.0
>
> Attachments: AMBARI-11922.patch
>
>
> Currently there is no way to determine which build a particular view is derived from.
It should be possible to determine this by introspecting the views' view.xml file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
|