[
https://issues.apache.org/jira/browse/NIFI-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15349865#comment-15349865
]
Joseph Witt commented on NIFI-2115:
-----------------------------------
Well, we could also consider as an alternative keeping 'about' pretty generic
and then adding a cluster topology type page which lists all this information
for each node. I am totally with you that this is useful.
As for the branching/commit info, the *only* thing we officially release is the
source release (the -src.zip). The convenience binaries are not the official
release. So with that in mind we could figure out a way to have this occur
during the source release process where by this i mean have it set some maven
properties. And those could be used when the unknown thing happens as you
outline below.
> Enhanced About Box Version Information
> --------------------------------------
>
> Key: NIFI-2115
> URL: https://issues.apache.org/jira/browse/NIFI-2115
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core UI, Tools and Build
> Affects Versions: 1.0.0
> Reporter: James Wing
> Assignee: James Wing
> Priority: Minor
>
> The UI's About dialog and underlying API provide the version of NiFi, like
> "0.7.0-SNAPSHOT". For many bug reports and troubleshooting requests, this is
> not very precise, especially around rapidly changing code or
> platform-dependent behavior. It would help if NiFi captured and displayed
> additional information:
> * NiFi build commit hash
> * NiFi build branch
> * NiFi build date/time
> * Java Version
> * Java Vendor (Oracle, OpenJDK)
> * OS
> Then a simple copy/paste from the about box would provide very specific
> information about a particular NiFi installation and which code it was
> derived from.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
