db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Bouschen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JDO-335) Close PMF after running each configuration
Date Sat, 11 Mar 2006 21:30:15 GMT
     [ http://issues.apache.org/jira/browse/JDO-335?page=all ]

Michael Bouschen updated JDO-335:
---------------------------------

    Attachment: JDO-335-2.patch

The new patch JDO-335-2.patch adds the system property jdo.tck.closePMFAfterEachTest to JDO_Test.
If set to true closePMF is called as part of tearDown, otherwise the pmf is closed at the
end of each configuration. The property defaults to false. It may be specified as -D option
on the maven call. 

I also changed the maven output at the end of each configuration to include the configuration
name.

> Close PMF after running each configuration
> ------------------------------------------
>
>          Key: JDO-335
>          URL: http://issues.apache.org/jira/browse/JDO-335
>      Project: JDO
>         Type: Improvement
>   Components: tck20
>     Versions: JDO 2 rc1
>     Reporter: Michael Bouschen
>     Assignee: Michael Bouschen
>     Priority: Minor
>      Fix For: JDO 2 final
>  Attachments: JDO-335-2.patch, JDO-335.patch
>
> Today method tearDown (that is run at the end of each test method) closes the pmf. 
> The proposal is to keep the pmf open for the next test method and close it at the end
of running a configuration. That would allow to reuse resources bound to the pmf in multiple
test cases.

-- 
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


Mime
View raw message