Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 75798 invoked from network); 1 Nov 2005 22:43:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 1 Nov 2005 22:43:15 -0000 Received: (qmail 35316 invoked by uid 500); 1 Nov 2005 22:43:14 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 35284 invoked by uid 500); 1 Nov 2005 22:43:14 -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 35275 invoked by uid 99); 1 Nov 2005 22:43:13 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of m.v.lunteren@gmail.com designates 64.233.162.201 as permitted sender) Received: from [64.233.162.201] (HELO zproxy.gmail.com) (64.233.162.201) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Nov 2005 14:43:13 -0800 Received: by zproxy.gmail.com with SMTP id s18so2282680nze for ; Tue, 01 Nov 2005 14:41:52 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=DNGXJvrj6FPKNOnuOFvFOLyOHblpBFCaib+dPeqRpFzWFEQEKhmPXqbvGiSfVhXvP+z7tXidt+Pt8tsMZMWr4PSq7ddKxUhCldBWkChV/qlpw+BLM/nwd92CVE65CPVE6igIOpSk408o8V/+jSpsdWmRhvEHe7U9Es7rFE3Wr0c= Received: by 10.36.9.13 with SMTP id 13mr4513994nzi; Tue, 01 Nov 2005 14:41:52 -0800 (PST) Received: by 10.36.13.20 with HTTP; Tue, 1 Nov 2005 14:41:52 -0800 (PST) Message-ID: Date: Tue, 1 Nov 2005 14:41:52 -0800 From: Myrna van Lunteren To: derby-dev@db.apache.org Subject: Re: POLL: Remove need for DB2 JDBC driver from Derby build and test In-Reply-To: <4367EA1C.1010604@sun.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_33282_20664550.1130884912759" References: <4367A018.4080702@amberpoint.com> <4367B236.7080309@amberpoint.com> <4367B976.7010003@amberpoint.com> <4367C496.3070005@sun.com> <4367C58C.9040708@debrunners.com> <4367EA1C.1010604@sun.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_33282_20664550.1130884912759 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I'd rather not spend time - making a patch and all that...- on it right now= . Maybe you can fix it and commit it too? (That is, you *are* a committer? Didn't see your name on: http://db.apache.org/whoweare.html) :-) Myrna On 11/1/05, David W. Van Couvering wrote: > > OK, that's good to know. It looks like I and others have been misled > that we had to pull these jars down to run tests. Note Bryan's recent > efforts to get these jars -- I think he was just following the > instructions in BUILDING.txt. > > I can log a JIRA to fix the wording in testing/README.htm to make it > clear that the DB2 driver is optional (and thus the derbynet tests are > optional). > > David > > Daniel John Debrunner wrote: > > David W. Van Couvering wrote: > > > > > >>I hope I'm not stepping on a landmine here, but does anyone else who > >>thinks it would be a good thing to remove the need for the DB2 JDBC > >>driver for our builds and tests? It's fine if it's an optional part, > >>like support for JDK 1.6, but it doesn't seem right that it's required > >>now that we have our own JDBC driver... > > > > > > Dumb question, in what way is it required? > > > > I thought it was alredy optional. > > > > As far as I know it is not needed for building. > > > > As far as I know the derbynet tests will be skipped if it is not in the > > class path. > > > > I thought that this had been the case since Derby was open sourced. > > > > Dan. > > > > > ------=_Part_33282_20664550.1130884912759 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
I'd rather not spend time - making a patch and all that...- on it righ= t now. Maybe you can fix it and commit it too?
(That is, you *are* a committer? Didn't see your name on: http://db.apache.org/whoweare.html)<= br> 
:-)
 
Myrna
 
On 11/1/05, = David W. Van Couvering <David.Vancouvering@sun.com> wrote:
OK, that's good to know. &n= bsp;It looks like I and others have been misled
that we had to pull thes= e jars down to run tests.  Note Bryan's recent
efforts to get these jars -- I think he was just following the
instr= uctions in BUILDING.txt.

I can log a JIRA to fix the wording in test= ing/README.htm to make it
clear that the DB2 driver is optional (and thu= s the derbynet tests are
optional).

David

Daniel John Debrunner wrote:
> Dav= id W. Van Couvering wrote:
>
>
>>I hope I'm not steppi= ng on a landmine here, but does anyone else who
>>thinks it would = be a good thing to remove the need for the DB2 JDBC
>>driver for our builds and tests?  It's fine if it's a= n optional part,
>>like support for JDK 1.6, but it doesn't seem r= ight that it's required
>>now that we have our own JDBC driver...<= br>>
>
> Dumb question, in what way is it required?
>
>= I thought it was alredy optional.
>
> As far as I know it is n= ot needed for building.
>
> As far as I know the derbynet tests= will be skipped if it is not in the
> class path.
>
> I thought that this had been the case = since Derby was open sourced.
>
> Dan.
>



------=_Part_33282_20664550.1130884912759--