Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 72712 invoked from network); 12 Mar 2007 17:27:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Mar 2007 17:27:31 -0000 Received: (qmail 82468 invoked by uid 500); 12 Mar 2007 17:27:39 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 82440 invoked by uid 500); 12 Mar 2007 17:27:39 -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 82430 invoked by uid 99); 12 Mar 2007 17:27:38 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Mar 2007 10:27:38 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Mar 2007 10:27:29 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 4275D714044 for ; Mon, 12 Mar 2007 10:27:09 -0700 (PDT) Message-ID: <6371419.1173720429252.JavaMail.jira@brutus> Date: Mon, 12 Mar 2007 10:27:09 -0700 (PDT) From: "Kristian Waagan (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Updated: (DERBY-2446) Remove notion of the old test harness from TestConfiguration In-Reply-To: <21123662.1173704169291.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-2446: ----------------------------------- Assignee: (was: Kristian Waagan) Thanks Dan. I notcied this when I ran the tests with Java 1.6. I think AutoloadBooting will be the most difficult one to fix. I guess we could live with moving LobStreamsTests, even though we might loose some testing coverage. I see an issue has been filed for rewriting the ComatibilityTest. I don't have the time to work on any of the related issues now, so I'm unassigning myself. Hopefully enough information has been collected for someone to pick this up later. > Remove notion of the old test harness from TestConfiguration > ------------------------------------------------------------ > > Key: DERBY-2446 > URL: https://issues.apache.org/jira/browse/DERBY-2446 > Project: Derby > Issue Type: Task > Components: Test > Affects Versions: 10.3.0.0 > Reporter: Kristian Waagan > Priority: Minor > > TestConfiguration has a notion of the old test harness. It is used when the old harness is running JUnit tests, and differs mostly by reading the system properties set by the harness and propagating these to the test configuration. > I found only one JUnit test being run from the harness; LobStreamsTest.junit. However, this is also run by the JUnit suite jdbcapi. > My suggestion is to remove the code related to the old harness in TestConfiguration and disable LobStreamsTest in derbynetclientmats. > A quick test showed that only LobStreamsTest failed when removing all the relevant code in TestConfiguration (ran both derbyall and suites.All). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.