You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Dmytro Shkvyra (JIRA)" <ji...@apache.org> on 2013/08/27 16:56:51 UTC

[jira] [Updated] (AMBARI-3036) Ambari version check failing for local development/VM

     [ https://issues.apache.org/jira/browse/AMBARI-3036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dmytro Shkvyra updated AMBARI-3036:
-----------------------------------

    Assignee: Dmytro Shkvyra
    
> 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
>
>
> 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