Mike Matrigali wrote:
It looks like a number of fixes have gone in, can this issue be closed?
The only working "fix" was to exclude the test from running in the DerbyNet framework, meaning that there is still an issue with the test. So perhaps this Jira should remain open, until the test itself has been fixed?
I don't understand the last two commits for DERBY-1691. To me they seem unrelated, and I suspect that there is a typo in the svn log message, DERBY-1691 instead of DERBY-1681.
-- John
