Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 11976 invoked from network); 24 May 2006 05:00:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 24 May 2006 05:00:12 -0000 Received: (qmail 4352 invoked by uid 500); 24 May 2006 05:00:11 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 4328 invoked by uid 500); 24 May 2006 05:00:11 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 4318 invoked by uid 99); 24 May 2006 05:00:10 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 May 2006 22:00:10 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 May 2006 22:00:10 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id A57D4714283 for ; Wed, 24 May 2006 04:59:30 +0000 (GMT) Message-ID: <9776033.1148446770675.JavaMail.jira@brutus> Date: Wed, 24 May 2006 04:59:30 +0000 (GMT+00:00) From: "Andrew McIntyre (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-892) add mechanism for specifying policy file for individual function tests In-Reply-To: <309953045.1138645843152.JavaMail.jira@ajax.apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/DERBY-892?page=comments#action_12413064 ] Andrew McIntyre commented on DERBY-892: --------------------------------------- This looks good, but shouldn't we leave the permissions needed for running tests in useprocess=false mode in the base harness policy file, considering the recent work that was done with DERBY-1141? Since the permission is only granted on derbyTesting.jar, the tests are still quite secure when running in from the jars. You could have the harness append the necessary permissions if running in useprocess=false mode, but that might be more trouble than its worth. Also, this makes the lang/errorStream.policy file unnecessary, unless you choose to go the append-permissions-for-useprocess=false route. > add mechanism for specifying policy file for individual function tests > ---------------------------------------------------------------------- > > Key: DERBY-892 > URL: http://issues.apache.org/jira/browse/DERBY-892 > Project: Derby > Type: Bug > Components: Test > Versions: 10.2.0.0 > Reporter: Myrna van Lunteren > Assignee: Myrna van Lunteren > Priority: Minor > Attachments: DERBY-892_20060514.diff, DERBY-892_20060514.stat, DERBY-892_3_20060523.diff, DERBY-892_3_20060523.stat, derby-892_pre.diff > > It would be nice to be able to specify a test-specific policy file. > This should get handled similar to existing properties, i.e. get specified in a test_app.properties file (or, for a suite, in the suite.properties file). The file should then be copied into the correct place. > Note, that the 'old' functionTests harness (as opposed to junit tests) includes a check for a property called 'serverPolicyFile' (in harness/jvm.java). The name is a left over from when the policy file was only used for/by network server, and should be renamed - derbyTestPolicyFile, for instance. It is not used anywhere at present, and not specific to network server. It would be nice if this could be expanded, or, if not used, removed. > The default policy file used is the derby_tests.policy file under functionTests/util. > Also, currently, the property can only be used with RunTest - for further traction, it should probably get passed on through RunSuite/RunList. > Once confirmed to be working, the property should get documented in /java/testing/README.htm. -- 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