You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-dev@db.apache.org by "Michelle Caisse (JIRA)" <ji...@apache.org> on 2005/09/22 18:18:36 UTC
[jira] Created: (JDO-145) Remove pm.deletePersistent from fieldtypes tests
Remove pm.deletePersistent from fieldtypes tests
------------------------------------------------
Key: JDO-145
URL: http://issues.apache.org/jira/browse/JDO-145
Project: JDO
Type: Bug
Components: tck20
Reporter: Michelle Caisse
Assigned to: Michelle Caisse
The fieldtypes tests delete the persistent instance that they create at the end of the test using pm.deletePersistent(). Now that we use the new cleanup mechanism (addTearDownClass(Class)), there is no reason to deletie the instance. Also, the new maven option jdo.tck.cleanupaftertest cannot override this cleanup, so you can never see the database contents for debugging. Therefore, we should remove the line that deletes the persistent instance.
--
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] Closed: (JDO-145) Remove pm.deletePersistent from fieldtypes
tests
Posted by "Michael Bouschen (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-145?page=all ]
Michael Bouschen closed JDO-145:
--------------------------------
Fix Version: JDO 2 beta
Resolution: Fixed
> Remove pm.deletePersistent from fieldtypes tests
> ------------------------------------------------
>
> Key: JDO-145
> URL: http://issues.apache.org/jira/browse/JDO-145
> Project: JDO
> Type: Bug
> Components: tck20
> Reporter: Michelle Caisse
> Assignee: Michelle Caisse
> Fix For: JDO 2 beta
>
> The fieldtypes tests delete the persistent instance that they create at the end of the test using pm.deletePersistent(). Now that we use the new cleanup mechanism (addTearDownClass(Class)), there is no reason to deletie the instance. Also, the new maven option jdo.tck.cleanupaftertest cannot override this cleanup, so you can never see the database contents for debugging. Therefore, we should remove the line that deletes the persistent instance.
--
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] Reopened: (JDO-145) Remove pm.deletePersistent from
fieldtypes tests
Posted by "Michael Bouschen (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-145?page=all ]
Michael Bouschen reopened JDO-145:
----------------------------------
> Remove pm.deletePersistent from fieldtypes tests
> ------------------------------------------------
>
> Key: JDO-145
> URL: http://issues.apache.org/jira/browse/JDO-145
> Project: JDO
> Type: Bug
> Components: tck20
> Reporter: Michelle Caisse
> Assignee: Michelle Caisse
>
> The fieldtypes tests delete the persistent instance that they create at the end of the test using pm.deletePersistent(). Now that we use the new cleanup mechanism (addTearDownClass(Class)), there is no reason to deletie the instance. Also, the new maven option jdo.tck.cleanupaftertest cannot override this cleanup, so you can never see the database contents for debugging. Therefore, we should remove the line that deletes the persistent instance.
--
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] Closed: (JDO-145) Remove pm.deletePersistent from fieldtypes tests
Posted by "Michelle Caisse (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-145?page=all ]
Michelle Caisse closed JDO-145:
-------------------------------
> Remove pm.deletePersistent from fieldtypes tests
> ------------------------------------------------
>
> Key: JDO-145
> URL: http://issues.apache.org/jira/browse/JDO-145
> Project: JDO
> Type: Bug
> Components: tck20
> Reporter: Michelle Caisse
> Assignee: Michelle Caisse
>
> The fieldtypes tests delete the persistent instance that they create at the end of the test using pm.deletePersistent(). Now that we use the new cleanup mechanism (addTearDownClass(Class)), there is no reason to deletie the instance. Also, the new maven option jdo.tck.cleanupaftertest cannot override this cleanup, so you can never see the database contents for debugging. Therefore, we should remove the line that deletes the persistent instance.
--
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] Resolved: (JDO-145) Remove pm.deletePersistent from fieldtypes tests
Posted by "Michelle Caisse (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-145?page=all ]
Michelle Caisse resolved JDO-145:
---------------------------------
Resolution: Fixed
revision 292259
> Remove pm.deletePersistent from fieldtypes tests
> ------------------------------------------------
>
> Key: JDO-145
> URL: http://issues.apache.org/jira/browse/JDO-145
> Project: JDO
> Type: Bug
> Components: tck20
> Reporter: Michelle Caisse
> Assignee: Michelle Caisse
>
> The fieldtypes tests delete the persistent instance that they create at the end of the test using pm.deletePersistent(). Now that we use the new cleanup mechanism (addTearDownClass(Class)), there is no reason to deletie the instance. Also, the new maven option jdo.tck.cleanupaftertest cannot override this cleanup, so you can never see the database contents for debugging. Therefore, we should remove the line that deletes the persistent instance.
--
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