Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <926189904.1228754686407.JavaMail.jira@brutus>
Date: Mon, 8 Dec 2008 08:44:46 -0800 (PST)
From: "Kathey Marsden (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Assigned: (DERBY-1135) Run upgrade test using a security
 manager
In-Reply-To: <269647436.1142982191698.JavaMail.jira@ajax>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kathey Marsden reassigned DERBY-1135:
-------------------------------------

    Assignee:     (was: Deepa Remesh)

> 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
>
> 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.
-
You can reply to this email to add a comment to the issue online.