[ http://issues.apache.org/jira/browse/DERBY-2000?page=comments#action_12448427 ] Knut Anders Hatlen commented on DERBY-2000: -------------------------------------------
I think it is reasonable that derby.jar is granted permission to create derby.system.home. +1 to commit. > A SecurityManager is not always installed when running JUnit tests/suites > ------------------------------------------------------------------------- > > Key: DERBY-2000 > URL: http://issues.apache.org/jira/browse/DERBY-2000 > Project: Derby > Issue Type: Bug > Components: Test > Affects Versions: 10.3.0.0 > Reporter: Kristian Waagan > Priority: Minor > Attachments: derby-2000-1a.diff > > > A SecurityManager is not always installed (early enough) when running JUnit > tests/suites. > For instance, when running 'jdbcapi.BlobClob4Blob' a SecurityManager was > installed during database boot and revealed problems with the policy file, > but when the same test was run as part of 'suites.All', no errors were seen. > BTW: There is nothing wrong with BlobClob4Blob. > It seems that 'BaseTestCase.runBare', which installs a SecurityManager, is > bypassed when running code in decorators (most importantly setUp). > Since a SecurityManager is installed as soon as a test method is run, this > bug is not that severe. -- 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
