Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of jta@bristowhill.com designates
 66.75.162.134 as permitted sender)
Message-ID: <44E50011.5000802@bristowhill.com>
Date: Thu, 17 Aug 2006 16:47:29 -0700
From: "Jean T. Anderson" <jta@bristowhill.com>
Reply-To: jta@bristowhill.com
User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc3 (X11/20050929)
MIME-Version: 1.0
To: derby-dev@db.apache.org
Subject: Re: db2jcc jar files (was Re: [jira] Commented: (DERBY-1691)
 jdbcapi/blobclob4BLOB.java
 fails under DerbyNet framework with JCC 2.6)
References: <8352917.1155839954330.JavaMail.jira@brutus>
 <44E4F97A.3000808@sun.com> <44E4FE2A.3070900@bristowhill.com>
In-Reply-To: <44E4FE2A.3070900@bristowhill.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Jean T. Anderson wrote:
> David Van Couvering wrote:
> 
>>Since failures in DerbyNet seem to be part of the overall regression
>>failures that people hit, it would be great if the db2jcc jar files were
>>just available rather than having to go through the process of
>>registering and installing Cloudscape to get the jars.
>>
>>Any reason these can't be checked into tools/java, as long as they are
>>not getting distributed in the release?  Or are there legal constraints?
> 
> Software under one of the Category A licenses listed at
> http://www.apache.org/legal/3party.html may be checked into an ASF svn
> repo. I don't think these qualify.

oh, wait, wait, not so fast I tell myself .... Category B also works --
we're talking about binaries. So anything that's Category A or B would
be fine.

  -jean