[
https://issues.apache.org/jira/browse/YETUS-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16202508#comment-16202508
]
Allen Wittenauer commented on YETUS-510:
----------------------------------------
{code}
make_version=$(${MAKE} --version | head -n 1 2>/dev/null)
{code}
Unfortunately, this isn't reliable.
e.g.:
{code}
sunos/i386 ryoko$ make --version
make: Warning: Ignoring DistributedMake -v option
make: Warning: Ignoring DistributedMake -o option
make: Fatal error: No dmake output dir argument after -o flag
{code}
I'd probably recommend:
* send stderr for make --version to /dev/null too
* check if make --version caused an error
* check if make --version even generated any output
Other than that, it seems reasonable.
> Build Tool report should include version
> ----------------------------------------
>
> Key: YETUS-510
> URL: https://issues.apache.org/jira/browse/YETUS-510
> Project: Yetus
> Issue Type: Improvement
> Components: Test Patch
> Affects Versions: 0.5.0
> Reporter: Mike Drob
> Assignee: Sean Busbey
> Priority: Critical
> Fix For: 0.6.0
>
> Attachments: YETUS-510.0.patch
>
>
> Example:
> https://issues.apache.org/jira/browse/HADOOP-14180?focusedCommentId=16022240&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16022240
> In the current build report output, Yetus will print the build tool used, but
> without a version number:
> || Subsystem||Report/Notes||
> |Build tool|maven|
> Instead it should specify the exact maven (or ant or whatever) version used,
> just in case the error ends up being related to the build tool.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
