[
https://issues.apache.org/jira/browse/OOZIE-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16197499#comment-16197499
]
Peter Cseh commented on OOZIE-2004:
-----------------------------------
Ohh, I've missed this during the review...
I've assumed that JsonTags.BUILD_VERSION and BuildInfo.BUILD_VERSION are the
same.
I'd prefer the second solution, it should be compatible enough for most use
cases. What do you think [~asasvari]?
> Improve Oozie version info output
> ---------------------------------
>
> Key: OOZIE-2004
> URL: https://issues.apache.org/jira/browse/OOZIE-2004
> Project: Oozie
> Issue Type: Improvement
> Components: build
> Affects Versions: 4.0.1
> Reporter: Chunjun Xiao
> Assignee: Artem Ervits
> Priority: Minor
> Fix For: 5.0.0
>
> Attachments: HBASE-2004-2.patch, OOZIE-2004-0.patch,
> OOZIE-2004-1.patch, OOZIE-2004-2.patch
>
>
> Current oozie version info output is quite simple:
> {code}
> [root@svm5 ~] # oozie version
> Oozie client build version: 4.0.1
> [root@svm5 ~] #
> {code}
> Can we improve it to follow the convention of Hadoop/HBase, as:
> {code}
> [root@svm5 ~] # oozie version
> Oozie 4.0.1
> Source code repository: ssh://git@XXX/oozie.git -r
> 3171cb656a4e4c1b2c1e9c6a47abed7df5bbcc8d
> Compiled by root on Sun Jul 6 04:38:08 PDT 2014
> From source with checksum XXX
> [root@svm5 ~] #
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
