You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Andrew McIntyre (JIRA)" <ji...@apache.org> on 2007/01/04 06:18:27 UTC

[jira] Commented: (DERBY-2044) Add date, derby version and jvm version info to the report generated by the top-level ant target junitreport.

    [ https://issues.apache.org/jira/browse/DERBY-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462128 ] 

Andrew McIntyre commented on DERBY-2044:
----------------------------------------

Attaching a patch which adds date and JVM vendor and version information to the Summary page, and captures the sysinfo output and links it into the upper right frame. Getting the Derby version into the report is going to be more difficult. I suppose we could just grab it from DBMS.properties if we assume we're always running from the classes dir, as I haven't really thought out how we will get the junitreport target to run against sane or insane jars yet. At least with this patch, the Derby version is just one click away in the sysinfo output.

Please review, if I don't hear any comments in a couple of days, I'll commit.

> Add date, derby version and jvm version info to the report generated by the top-level ant target junitreport.
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2044
>                 URL: https://issues.apache.org/jira/browse/DERBY-2044
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools, Test
>            Reporter: Daniel John Debrunner
>         Assigned To: Andrew McIntyre
>         Attachments: derby-2044-v1.diff
>
>
> The HTML report is a great beginning but it is lacking some information on the summary page. I think this info would be useful.
> Date of the run
> Version information for Derby
> JVM version information
> Ideally a brief summary at the top-level, maybe a separate page could have the full detail, such as sysinfo output.
> Possible could be done using the style sheets rather than modifying the task, my xsl ability was limited to changing the
> heading from "Unit Test" to "Apache Derby Testing" :-)
> Was thinking the junit-init target could generate the correct data and the style sheet incorporate it.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira