[
https://issues.apache.org/jira/browse/DERBY-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew McIntyre resolved DERBY-2044.
------------------------------------
Resolution: Fixed
Fix Version/s: 10.3.0.0
Derby Info: (was: [Patch Available])
Committed to trunk with revision 492923, including John's suggestion of adding
the timezone. I'm still thinking of ways to get the Derby version onto the
front page, considering all the different possible usage scenarios (classpath,
sane/insane jars, snapshots, and releases), and will try to include it along
with the fix for DERBY-2045.
> 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
> Fix For: 10.3.0.0
>
> 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
