[jira] [Commented] (OOZIE-2004) Improve Oozie version info output
[ https://issues.apache.org/jira/browse/OOZIE-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16198692#comment-16198692 ] Peter Cseh commented on OOZIE-2004: --- Yes, that would be correct [~dbist13]. I've opened up OOZIE-3083 to track this. > 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)
[jira] [Commented] (OOZIE-2004) Improve Oozie version info output
[ https://issues.apache.org/jira/browse/OOZIE-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16197617#comment-16197617 ] Artem Ervits commented on OOZIE-2004: - [~asasvari] shouldn't it then be like so: {code} {"buildVersion":"5.0.0-SNAPSHOT", "buildInfo":"{build.time=${build.time}, vc.url=${vc.url}, build.user=asasvari, vc.revision=${vc.revision}"} {code} > 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)
[jira] [Commented] (OOZIE-2004) Improve Oozie version info output
[ 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)
[jira] [Commented] (OOZIE-2004) Improve Oozie version info output
[ https://issues.apache.org/jira/browse/OOZIE-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16197222#comment-16197222 ] Attila Sasvari commented on OOZIE-2004: --- This change breaks API compatibility. Existing clients of the Oozie server that depend on {{/v1/admin/build-version}} will break without a client-side update. For example, a monitoring client might depend on the {{buildVersion}} element in the returned JSON. Right now the server returns: {code} {"buildInfo":"{build.time=${build.time}, vc.url=${vc.url}, build.user=asasvari, vc.revision=${vc.revision}, build.version=5.0.0-SNAPSHOT}"} {code} It would be better to have either a new version {{/v3/admin/build-version}} or only add content like: {code} {"buildVersion":"5.0.0-SNAPSHOT", "buildInfo":"{build.time=${build.time}, vc.url=${vc.url}, build.user=asasvari, vc.revision=${vc.revision}, build.version=5.0.0-SNAPSHOT}"} {code} > 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)
[jira] [Commented] (OOZIE-2004) Improve Oozie version info output
[ https://issues.apache.org/jira/browse/OOZIE-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16086966#comment-16086966 ] Peter Cseh commented on OOZIE-2004: --- +1 > 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)
[jira] [Commented] (OOZIE-2004) Improve Oozie version info output
[ https://issues.apache.org/jira/browse/OOZIE-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16085878#comment-16085878 ] Artem Ervits commented on OOZIE-2004: - [~gezapeti] please review, failing tests are unrelated and pass locally. > 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)
[jira] [Commented] (OOZIE-2004) Improve Oozie version info output
[ https://issues.apache.org/jira/browse/OOZIE-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16085830#comment-16085830 ] Hadoop QA commented on OOZIE-2004: -- Testing JIRA OOZIE-2004 Cleaning local git workspace {color:green}+1 PATCH_APPLIES{color} {color:green}+1 CLEAN{color} {color:green}+1 RAW_PATCH_ANALYSIS{color} .{color:green}+1{color} the patch does not introduce any @author tags .{color:green}+1{color} the patch does not introduce any tabs .{color:green}+1{color} the patch does not introduce any trailing spaces .{color:green}+1{color} the patch does not introduce any line longer than 132 .{color:green}+1{color} the patch does adds/modifies 4 testcase(s) {color:green}+1 RAT{color} .{color:green}+1{color} the patch does not seem to introduce new RAT warnings {color:green}+1 JAVADOC{color} .{color:green}+1{color} the patch does not seem to introduce new Javadoc warnings .{color:red}WARNING{color}: the current HEAD has 1 Javadoc warning(s) {color:green}+1 COMPILE{color} .{color:green}+1{color} HEAD compiles .{color:green}+1{color} patch compiles .{color:green}+1{color} the patch does not seem to introduce new javac warnings {color:green}+1{color} There are no new bugs found in total. {color:green}+1 BACKWARDS_COMPATIBILITY{color} .{color:green}+1{color} the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations .{color:green}+1{color} the patch does not modify JPA files {color:green}+1 TESTS{color} .Tests run: 957 .Tests rerun: 3 .Tests failed at first run: org.apache.oozie.action.hadoop.TestHdfsOperations, {color:green}+1 DISTRO{color} .{color:green}+1{color} distro tarball builds with the patch {color:green}*+1 Overall result, good!, no -1s*{color} {color:red}. There is at least one warning, please check{color} The full output of the test-patch run is available at . https://builds.apache.org/job/oozie-trunk-precommit-build/3972/ > 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)
[jira] [Commented] (OOZIE-2004) Improve Oozie version info output
[ https://issues.apache.org/jira/browse/OOZIE-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16085663#comment-16085663 ] Artem Ervits commented on OOZIE-2004: - [~gezapeti] uploaded new patch, thanks for the catch! > 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)
[jira] [Commented] (OOZIE-2004) Improve Oozie version info output
[ https://issues.apache.org/jira/browse/OOZIE-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16083603#comment-16083603 ] Peter Cseh commented on OOZIE-2004: --- Thnaks for the improvement! In OozieCLI you've accidentally escaped the newline charactes: {{ .append("\\nSource code repository: ")}} So I get the output: {code} >> [61] 09:41 : oozie-client-5.0.0-SNAPSHOT (master) :: ./bin/oozie version Oozie client build version: 5.0.0-SNAPSHOT\nSource code repository: https://git-wip-us.apache.org/repos/asf/oozie.git\nCompiled by gezapeti on 2017.07.12-07:33:26GMT\nFrom source with checksum: master@a54f7c20 {code} > 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 > > > 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)
[jira] [Commented] (OOZIE-2004) Improve Oozie version info output
[ https://issues.apache.org/jira/browse/OOZIE-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16082457#comment-16082457 ] Artem Ervits commented on OOZIE-2004: - [~rkanter] [~gezapeti] can I get a yay or nay on this, I have some bandwidth and want to close some of my issues in "patch available" stage. > 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 > > > 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)
[jira] [Commented] (OOZIE-2004) Improve Oozie version info output
[ https://issues.apache.org/jira/browse/OOZIE-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16065771#comment-16065771 ] Artem Ervits commented on OOZIE-2004: - failing test is unrelated > 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 > > > 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)
[jira] [Commented] (OOZIE-2004) Improve Oozie version info output
[ https://issues.apache.org/jira/browse/OOZIE-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16065341#comment-16065341 ] Hadoop QA commented on OOZIE-2004: -- Testing JIRA OOZIE-2004 Cleaning local git workspace {color:green}+1 PATCH_APPLIES{color} {color:green}+1 CLEAN{color} {color:green}+1 RAW_PATCH_ANALYSIS{color} .{color:green}+1{color} the patch does not introduce any @author tags .{color:green}+1{color} the patch does not introduce any tabs .{color:green}+1{color} the patch does not introduce any trailing spaces .{color:green}+1{color} the patch does not introduce any line longer than 132 .{color:green}+1{color} the patch does adds/modifies 4 testcase(s) {color:green}+1 RAT{color} .{color:green}+1{color} the patch does not seem to introduce new RAT warnings {color:green}+1 JAVADOC{color} .{color:green}+1{color} the patch does not seem to introduce new Javadoc warnings .{color:red}WARNING{color}: the current HEAD has 1 Javadoc warning(s) {color:green}+1 COMPILE{color} .{color:green}+1{color} HEAD compiles .{color:green}+1{color} patch compiles .{color:green}+1{color} the patch does not seem to introduce new javac warnings {color:green}+1{color} There are no new bugs found in total. {color:green}+1 BACKWARDS_COMPATIBILITY{color} .{color:green}+1{color} the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations .{color:green}+1{color} the patch does not modify JPA files {color:red}-1 TESTS{color} .Tests run: 1968 .Tests failed: 0 .Tests errors: 1 .The patch failed the following testcases: . .Tests failing with errors: . testJMXInstrumentation(org.apache.oozie.util.TestMetricsInstrumentation) {color:green}+1 DISTRO{color} .{color:green}+1{color} distro tarball builds with the patch {color:red}*-1 Overall result, please check the reported -1(s)*{color} {color:red}. There is at least one warning, please check{color} The full output of the test-patch run is available at . https://builds.apache.org/job/oozie-trunk-precommit-build/3929/ > 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 > > > 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)
[jira] [Commented] (OOZIE-2004) Improve Oozie version info output
[ https://issues.apache.org/jira/browse/OOZIE-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16065082#comment-16065082 ] Hadoop QA commented on OOZIE-2004: -- Testing JIRA OOZIE-2004 Cleaning local git workspace {color:green}+1 PATCH_APPLIES{color} {color:green}+1 CLEAN{color} {color:green}+1 RAW_PATCH_ANALYSIS{color} .{color:green}+1{color} the patch does not introduce any @author tags .{color:green}+1{color} the patch does not introduce any tabs .{color:green}+1{color} the patch does not introduce any trailing spaces .{color:green}+1{color} the patch does not introduce any line longer than 132 .{color:green}+1{color} the patch does adds/modifies 3 testcase(s) {color:green}+1 RAT{color} .{color:green}+1{color} the patch does not seem to introduce new RAT warnings {color:green}+1 JAVADOC{color} .{color:green}+1{color} the patch does not seem to introduce new Javadoc warnings .{color:red}WARNING{color}: the current HEAD has 1 Javadoc warning(s) {color:green}+1 COMPILE{color} .{color:green}+1{color} HEAD compiles .{color:green}+1{color} patch compiles .{color:green}+1{color} the patch does not seem to introduce new javac warnings {color:green}+1{color} There are no new bugs found in total. {color:green}+1 BACKWARDS_COMPATIBILITY{color} .{color:green}+1{color} the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations .{color:green}+1{color} the patch does not modify JPA files {color:red}-1 TESTS{color} .Tests run: 1968 .Tests failed: 1 .Tests errors: 0 .The patch failed the following testcases: . testServerBuildVersion(org.apache.oozie.client.TestWorkflowClient) .Tests failing with errors: . {color:green}+1 DISTRO{color} .{color:green}+1{color} distro tarball builds with the patch {color:red}*-1 Overall result, please check the reported -1(s)*{color} {color:red}. There is at least one warning, please check{color} The full output of the test-patch run is available at . https://builds.apache.org/job/oozie-trunk-precommit-build/3928/ > 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: OOZIE-2004-0.patch, OOZIE-2004-1.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)
[jira] [Commented] (OOZIE-2004) Improve Oozie version info output
[ https://issues.apache.org/jira/browse/OOZIE-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064633#comment-16064633 ] Peter Cseh commented on OOZIE-2004: --- Thanks for the contribution! I think updating the admin servlet as well would be great! Instead of returning only the build version, we could pass the whole properties object as a json in [BaseAdminServlet|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/servlet/BaseAdminServlet.java#L149] > 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: OOZIE-2004-0.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)
[jira] [Commented] (OOZIE-2004) Improve Oozie version info output
[ https://issues.apache.org/jira/browse/OOZIE-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16060840#comment-16060840 ] Artem Ervits commented on OOZIE-2004: - tests passing locally > 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: OOZIE-2004-0.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)
[jira] [Commented] (OOZIE-2004) Improve Oozie version info output
[ https://issues.apache.org/jira/browse/OOZIE-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16060420#comment-16060420 ] Hadoop QA commented on OOZIE-2004: -- Testing JIRA OOZIE-2004 Cleaning local git workspace {color:green}+1 PATCH_APPLIES{color} {color:green}+1 CLEAN{color} {color:green}+1 RAW_PATCH_ANALYSIS{color} .{color:green}+1{color} the patch does not introduce any @author tags .{color:green}+1{color} the patch does not introduce any tabs .{color:green}+1{color} the patch does not introduce any trailing spaces .{color:green}+1{color} the patch does not introduce any line longer than 132 .{color:green}+1{color} the patch does adds/modifies 1 testcase(s) {color:green}+1 RAT{color} .{color:green}+1{color} the patch does not seem to introduce new RAT warnings {color:green}+1 JAVADOC{color} .{color:green}+1{color} the patch does not seem to introduce new Javadoc warnings .{color:red}WARNING{color}: the current HEAD has 1 Javadoc warning(s) {color:green}+1 COMPILE{color} .{color:green}+1{color} HEAD compiles .{color:green}+1{color} patch compiles .{color:green}+1{color} the patch does not seem to introduce new javac warnings {color:green}+1{color} There are no new bugs found in total. {color:green}+1 BACKWARDS_COMPATIBILITY{color} .{color:green}+1{color} the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations .{color:green}+1{color} the patch does not modify JPA files {color:green}+1 TESTS{color} .Tests run: 1968 .Tests rerun: 79 .Tests failed at first run: org.apache.oozie.action.hadoop.TestJavaActionExecutor,org.apache.oozie.jms.TestJMSJobEventListener,org.apache.oozie.action.hadoop.TestLauncherAM, {color:green}+1 DISTRO{color} .{color:green}+1{color} distro tarball builds with the patch {color:green}*+1 Overall result, good!, no -1s*{color} {color:red}. There is at least one warning, please check{color} The full output of the test-patch run is available at . https://builds.apache.org/job/oozie-trunk-precommit-build/3924/ > 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: OOZIE-2004-0.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)