[
https://issues.apache.org/jira/browse/OOZIE-3152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16315101#comment-16315101
]
Attila Sasvari commented on OOZIE-3152:
---------------------------------------
[~andras.piros] thanks for your answer. I still believe we shall not introduce
this kind of workarounds. The real problem is that the response of
{{v2/admin/build-version}} is not a JSON object. {{BaseAdminServlet}} should be
fixed so that it uses ObjectMapper or something to return [valid JSON
output|http://www.json.org/] for {{build.info}} too (use colon intead of =).
OOZIE-3083 is almost finished.
> Oozie version is undefined in UI
> --------------------------------
>
> Key: OOZIE-3152
> URL: https://issues.apache.org/jira/browse/OOZIE-3152
> Project: Oozie
> Issue Type: Bug
> Reporter: Satish Subhashrao Saley
> Assignee: Julia Kinga Marton
> Priority: Blocker
> Labels: newbie
> Fix For: 5.0.0b1, 5.0.0
>
> Attachments: OOZIE-3152-001.patch, OOZIE-3152-002.patch, Screen Shot
> 2018-01-03 at 3.33.58 PM.png, ServerVersionAdded.png
>
>
> The json string returned by
> http://localhost:11000/oozie/v2/admin/build-version
> {code}
> {
> buildInfo: "{build.time=${build.time}, vc.url=${vc.url}, build.user=saley,
> vc.revision=${vc.revision}, build.version=5.0.0-beta1}"
> }
> {code}
> We need to read the version properly here -
> https://github.com/apache/oozie/blob/master/webapp/src/main/webapp/oozie-console.js#L2713
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
