Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 46458 invoked from network); 30 Jul 2006 05:23:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 30 Jul 2006 05:23:50 -0000 Received: (qmail 82694 invoked by uid 500); 30 Jul 2006 05:23:49 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 82660 invoked by uid 500); 30 Jul 2006 05:23:49 -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 82647 invoked by uid 99); 30 Jul 2006 05:23:49 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 29 Jul 2006 22:23:49 -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; Sat, 29 Jul 2006 22:23:47 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 0348871428E for ; Sun, 30 Jul 2006 05:21:15 +0000 (GMT) Message-ID: <13757664.1154236875011.JavaMail.jira@brutus> Date: Sat, 29 Jul 2006 22:21:15 -0700 (PDT) From: "Myrna van Lunteren (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Updated: (DERBY-1091) Test harness does not pass jvm flags properly if there are more than 1 property in jvm flags In-Reply-To: <91884638.1141855613076.JavaMail.jira@ajax> 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-1091?page=all ] Myrna van Lunteren updated DERBY-1091: -------------------------------------- Attachment: DERBY-1091_20060729.diff Fixing the regression with j2ME I caused...with DERBY-1091_20060729.diff. > Test harness does not pass jvm flags properly if there are more than 1 property in jvm flags > -------------------------------------------------------------------------------------------- > > Key: DERBY-1091 > URL: http://issues.apache.org/jira/browse/DERBY-1091 > Project: Derby > Issue Type: Test > Components: Test > Affects Versions: 10.2.0.0 > Environment: Windows 2000 > Reporter: Ramandeep Kaur > Assigned To: Myrna van Lunteren > Priority: Minor > Fix For: 10.2.0.0 > > Attachments: DERBY-1091_20060702.diff, DERBY-1091_20060702.stat, DERBY-1091_20060729.diff > > > To run Derby tests with EMMA for Code coverage, there is a need to set up emma flag -Djvmflags=-Demma.verbosity.level=silent. This is basically to enable EMMA not to print out any messages to avoid having any diffs. This all works fine when running Derby tests with EMMA for jdk142, jdk15, jdk131 etc because there is no other jvm flag that is passed while calling RunSuite Command. > Now, while running tests with j2me/cdc/foundation, another value needs to be passed as jvmflag which is > -Djvmflags="Dij.dataSource=org.apache.derby.jdbc.EmbeddedSimpleDataSource". > I tried to combine values for both jvm flags as following, but it did not work properly: > 1. -Djvmflags='-Demma.verbosity.level=silent -Dij.dataSource=org.apache.derby.jdbc.EmbeddedSimpleDataSource' > During this run, the value that was further passed while running one test was Djvmflags="'-Demma.verbosity.level=silent". > As you can notice it took jvm flag as '-Demma.verbosity.level=silent > 2. -Djvmflags="-Demma.verbosity.level=silent -Dij.dataSource=org.apache.derby.jdbc.EmbeddedSimpleDataSource" > During this run, the value that was further passed while running one test was Djvmflags=""-Demma.verbosity.level=silent". > As you can notice it took jvm flag as "-Demma.verbosity.level=silent > From the above it looks like test harness needs to be changed so that it can parse multiple values for jvm flags properly. -- 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