[
https://issues.apache.org/jira/browse/DERBY-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren updated DERBY-1552:
--------------------------------------
Labels: derby_triage10_8 (was: )
Issue Type: Improvement (was: Bug)
Still valid with notes...
dbjarUtil is currently used in junit test ...lang.DBInjarTest and old style
tests store/encryptDatabaseTest3 and store/encryptKey_jar.
Once privileged blocks are added, DBInjarTest can be made to run under security
manager (by removing the call to SecurityManagerSetup.noSecurityManager).
And we should convert encryptKey_jar (and encryptDatabaseTest3) to junit rather
than modify it to run as is under security manager.
> Add privileged blocks to test/lang/dbjarUtil.
> ---------------------------------------------
>
> Key: DERBY-1552
> URL: https://issues.apache.org/jira/browse/DERBY-1552
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.2.1.6
> Reporter: Sunitha Kambhampati
> Priority: Minor
> Labels: derby_triage10_8
>
> Add privileged blocks to code in tests/lang/dbjarUtil.java.
> consider if it is good to push this class to tests/util directory since it is
> used by a test in lang suite and the encryptionKey_jar.sql is under store
> tests.
> once this is fixed, also enable the security manager for encryptionKey_jar.sql
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
