db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michelle Caisse (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JDO-300) Log system and jvm version information with test results
Date Sat, 04 Mar 2006 00:42:40 GMT
     [ http://issues.apache.org/jira/browse/JDO-300?page=all ]

Michelle Caisse updated JDO-300:

    Attachment: JDO-300.patch

Created a new java utility class to write all System properties to a file in the logs/<timestamp>/configuration
directory. Added some lines in the result goal of maven.xml to invoke the class.

Also moved <attainGoal name="result"> from the build and two runtck goals to the two
privateRuntck goals.

> Log system and jvm version information with test results
> --------------------------------------------------------
>          Key: JDO-300
>          URL: http://issues.apache.org/jira/browse/JDO-300
>      Project: JDO
>         Type: Improvement
>   Components: tck20
>     Versions: JDO 2 beta
>     Reporter: Michelle Caisse
>     Assignee: Michelle Caisse
>      Fix For: JDO 2 final
>  Attachments: JDO-300.patch
> In order to capture complete environment information with a test run for certification
and debugging, capture information about the host system and the jvm and write to the log/.../configuration
directory for the test run. This could be implemented in maven using java -version and uname
calls, or could be implemented as a special-purpose junit test where the latter records the
values of the relevant java system properties, such as java.version, os.name... The latter
approach is more easily made independent of the OS the test run is performed on.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message