Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ambari-dev@incubator.apache.org
Date: Tue, 27 Aug 2013 15:06:52 +0000 (UTC)
From: "Oleksandr Diachenko (JIRA)" <jira@apache.org>
To: ambari-dev@incubator.apache.org
Message-ID: <JIRA.12665726.1377615329513.39753.1377616012939@arcas>
In-Reply-To: <JIRA.12665726.1377615329513@arcas>
References: <JIRA.12665726.1377615329513@arcas>
Subject: [jira] [Commented] (AMBARI-3036) Ambari version check failing for
 local development/VM
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/AMBARI-3036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13751337#comment-13751337 ] 

Oleksandr Diachenko commented on AMBARI-3036:
---------------------------------------------

+1
                
> Ambari version check failing for local development/VM
> -----------------------------------------------------
>
>                 Key: AMBARI-3036
>                 URL: https://issues.apache.org/jira/browse/AMBARI-3036
>             Project: Ambari
>          Issue Type: Bug
>          Components: controller
>            Reporter: Dmytro Shkvyra
>            Assignee: Dmytro Shkvyra
>             Fix For: 1.4.1
>
>         Attachments: AMBARI-3036.patch
>
>
> When running ambari from trunk, connecting to a local VM, the version check relies on a numeric version (x.x.x). However, the version file contains only $
> {ambariVersion}
> which is replaced at build time, making dev environs difficult to setup.
> The version check should first do a string compare for equality, which is likely the most common case

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira