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 "Daniel John Debrunner (JIRA)" <ji...@apache.org> on 2006/11/04 02:17:16 UTC

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

Add date, derby version and jvm version info to the report generated by the top-level ant target junitreport.
-------------------------------------------------------------------------------------------------------------

                 Key: DERBY-2044
                 URL: http://issues.apache.org/jira/browse/DERBY-2044
             Project: Derby
          Issue Type: Improvement
          Components: Build tools, Test
            Reporter: Daniel John Debrunner


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: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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

Posted by "John H. Embretsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DERBY-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462234 ] 

John H. Embretsen commented on DERBY-2044:
------------------------------------------

I tried this patch, testing the classes/ directory (Ant 1.6.5), and the report looks good to me. I think including the timezone (zzz) to the timestamp would be useful once people start sharing test reports, this being a relatively dispersed international community.

> 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

        

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

Posted by "Andrew McIntyre (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew McIntyre updated DERBY-2044:
-----------------------------------

    Derby Info: [Patch Available]

> 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

        

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

Posted by "Andrew McIntyre (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew McIntyre reassigned DERBY-2044:
--------------------------------------

    Assignee: Andrew McIntyre

> 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

        

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

Posted by "Andrew McIntyre (JIRA)" <ji...@apache.org>.
    [ 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

        

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

Posted by "Andrew McIntyre (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew McIntyre updated DERBY-2044:
-----------------------------------

    Attachment: derby-2044-v1.diff

> 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

        

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

Posted by "Andrew McIntyre (JIRA)" <ji...@apache.org>.
     [ 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

        

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

Posted by "Dyre Tjeldvoll (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dyre Tjeldvoll closed DERBY-2044.
---------------------------------


> 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
>            Assignee: Andrew McIntyre
>             Fix For: 10.3.1.4
>
>         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.
-
You can reply to this email to add a comment to the issue online.