You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <de...@db.apache.org> on 2006/09/19 16:59:28 UTC
[jira] Updated: (DERBY-1135) Run upgrade test using a security
manager
[ http://issues.apache.org/jira/browse/DERBY-1135?page=all ]
Rick Hillegas updated DERBY-1135:
---------------------------------
Fix Version/s: 10.2.2.0
(was: 10.2.1.0)
Moving to 10.2.2.0.
> Run upgrade test using a security manager
> -----------------------------------------
>
> Key: DERBY-1135
> URL: http://issues.apache.org/jira/browse/DERBY-1135
> Project: Derby
> Issue Type: Sub-task
> Components: Test
> Reporter: Deepa Remesh
> Assigned To: Deepa Remesh
> Fix For: 10.2.2.0
>
>
> 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.
-
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