db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Closed: (DERBY-1135) Run upgrade test using a security manager
Date Fri, 04 Feb 2011 01:03:23 GMT

     [ https://issues.apache.org/jira/browse/DERBY-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Myrna van Lunteren closed DERBY-1135.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.3.1.4

The current junit upgrade tests run under Security Manager, so this was fixed with the conversion
to Junit (DERBY-2217). Setting to fixed in the same version as that one.

> Run upgrade test using a security manager
> -----------------------------------------
>
>                 Key: DERBY-1135
>                 URL: https://issues.apache.org/jira/browse/DERBY-1135
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Test
>            Reporter: Deepa Remesh
>             Fix For: 10.3.1.4
>
>
> To be able to run the upgrade test using the test harness, it should be possible to run
the test using the harness' security manager. Some issues in doing this are identified in
http://www.nabble.com/Upgrade-test-and-security-permissions-p3517019.html. We need to identify
the set of permissions required to run the test. This seems to a slightly more involved task
because of use of jars from multiple versions. Hence opening it as a sub-task.
> As a temporary solution, I think we can add "noSecurityManager=true" to allow the test
to run in the harness.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message