[
https://issues.apache.org/jira/browse/AMBARI-17282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15335022#comment-15335022
]
Hudson commented on AMBARI-17282:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #5096 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5096/])
AMBARI-17282. Use customized display name as version string (ncole) (ncole:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a94ebcfb64c27fa668aa5527090cf9b0f35537e1])
*
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/VersionDefinitionResourceProviderTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/VersionDefinitionResourceProvider.java
> Use customized display name as version string
> ---------------------------------------------
>
> Key: AMBARI-17282
> URL: https://issues.apache.org/jira/browse/AMBARI-17282
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Reporter: Nate Cole
> Assignee: Nate Cole
> Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17282.patch
>
>
> The user can specify the display name when creating a version using VDF. In
> that case, use that for the repository version string as well. This does not
> cause problems as the version will get replaced at install time. We just
> need a way to provide uniqueness in the DB.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
