[
https://issues.apache.org/jira/browse/YETUS-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16203732#comment-16203732
]
Allen Wittenauer commented on YETUS-510:
----------------------------------------
Unfortunately, -v and -V for some versions of make are legal options that don't
return version numbers. For example, dmake uses -v for verbosity, but -V does
return the version. But BSD make uses -V for variable definition verification.
(e.g., "if I process this Makefile, what will foo be defined as?") It then
turns into a game of "did we actually get a version number or something else?"
In other words, anything other --version is going to be very hit or miss and
the chances for false positives are high. The vast majority of non-GNU make
tools don't really have a way to return a version number anyway; the version
number is effectively the OS patch level version.
One other thing: should we drop and/or combine the buildtool field in the
footer if we're going to report this version? It'd reduce the output.
> 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)
