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

Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/05/31 21:41:00 UTC

[jira] [Commented] (AMBARI-24000) Fix ambari-web pom.xml (version not updated correctly)

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

Hudson commented on AMBARI-24000:
---------------------------------

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9380 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9380/])
AMBARI-24000. Fix ambari-web pom.xml (version not updated correctly). (yusaku: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=2d82dd89d6352b7fe3aaae7b6abdde55eeea9bdc])
* (edit) ambari-web/pom.xml


> Fix ambari-web pom.xml (version not updated correctly)
> ------------------------------------------------------
>
>                 Key: AMBARI-24000
>                 URL: https://issues.apache.org/jira/browse/AMBARI-24000
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.7.0
>            Reporter: Yusaku Sako
>            Assignee: Yusaku Sako
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 2.7.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> ambari-web/pom.xml is hardcoding the version to 2.99.99.
> This needs to be fixed so that it can be overwritten correctly when mvn versions:set is run from the top-level directory.  Current pom.xml leaves the Ambari Web version to 2.99.99 even after the command is run.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)