Jonas S Karlsson wrote:
A small "cosmetic" patch for derby.
When ij/derby is started it creates the file derby.log and this file
contains an error message as follows:
2004-09-28 23:11:50.428 GMT Thread[main,5,main] Class com.ibm.derby.impl.BasicServices.TestService.Basic.BasicUnitTestManager java.lang.ClassNotFoundException: com.ibm.derby.impl.BasicServices.TestService.Basic.BasicUnitTestManager, module ignored.
----------------------------------------------------------------
No class com.ibm.derby... exists so it seems to be a misnomer.
The message doesn't seem to cause any other errors but it doesn't
look good in the log file.
So here is a small patch:
------ begin patch ---
Index: java/engine/org/apache/derby/modules.properties
===================================================================
--- java/engine/org/apache/derby/modules.properties (revision 47434)
+++ java/engine/org/apache/derby/modules.properties (working copy)
@@ -123,7 +123,6 @@
derby.module.lockManager=org.apache.derby.impl.services.locks.SinglePool
cloudscape.config.lockManager=all
-derby.module.testManager=com.ibm.derby.impl.BasicServices.TestService.Basic.BasicUnitTestManager
cloudscape.config.testManager=none
derby.module.classManagerJ2=org.apache.derby.impl.services.reflect.ReflectClassesJava2
------ end patch ---
BTW, this file is full of "cloudscape.config" strings, my guess is that
this too should be fixed somewhere and somehow, or removed.
/Jonas
The "cloudscape.config.testManager=none" line should also be removed.
It is used to describe the configurations that should contain the
corresponding derby.module.testManager module. Since the
derby.module.testManager property is being removed the
cloudscape.config.testManager property should also be removed; it is
meaningless without the derby.module.testManager property.
Jack Klebanoff
|
