Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 83430 invoked from network); 16 Nov 2007 16:22:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 16 Nov 2007 16:22:06 -0000 Received: (qmail 53107 invoked by uid 500); 16 Nov 2007 16:21:51 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 53075 invoked by uid 500); 16 Nov 2007 16:21:51 -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 53061 invoked by uid 99); 16 Nov 2007 16:21:51 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Nov 2007 08:21:51 -0800 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED 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; Fri, 16 Nov 2007 16:21:50 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id B1B9F714254 for ; Fri, 16 Nov 2007 08:21:43 -0800 (PST) Message-ID: <27735302.1195230103725.JavaMail.jira@brutus> Date: Fri, 16 Nov 2007 08:21:43 -0800 (PST) From: "Dyre Tjeldvoll (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-2807) Create a test for BlobClob compatibility on Derby server versions vs. Derby client versions. In-Reply-To: <13442226.1181641406119.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-2807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543125 ] Dyre Tjeldvoll commented on DERBY-2807: --------------------------------------- Seems like this patch has been sitting for a while. Should it be committed as is, or is it possible to add some logic that detects that the test is not run through the CompatibilityCombinations framework? Almost anything would be better than an NPE, I guess... > Create a test for BlobClob compatibility on Derby server versions vs. Derby client versions. > -------------------------------------------------------------------------------------------- > > Key: DERBY-2807 > URL: https://issues.apache.org/jira/browse/DERBY-2807 > Project: Derby > Issue Type: Improvement > Components: Test > Affects Versions: 10.3.1.4 > Reporter: Ole Solberg > Assignee: Ole Solberg > Priority: Minor > Attachments: compatibilitytest.properties, derby-2807-v1.diff.txt > > > Run '..../tests/jdbcapi/BlobClob4BlobTest.java' in the 'java/testing/org/apache/derbyTesting/functionTests/tests/junitTests/compatibility/CompatibilityCombinations.java' framework to test combinations of Derby server versions vs. Derby client versions. The CompatibilityCombinations framework also allows varying the JVM version used on the server and client side. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.