Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
Mime-Version: 1.0 (Apple Message framework v619)
In-Reply-To: <779008E5-1C77-11D9-906D-003065905854@nonintuitive.com>
References: <4420A5C4-17DE-11D9-A78E-003065CBB010@nonintuitive.com>
 <0EA06A90-1C23-11D9-906D-003065905854@nonintuitive.com>
 <ED3B4245-1C47-11D9-9D12-000A959CB3F2@mac.com>
 <779008E5-1C77-11D9-906D-003065905854@nonintuitive.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <0B28D958-1C8B-11D9-9D12-000A959CB3F2@mac.com>
Content-Transfer-Encoding: 7bit
From: Dick Applebaum <dicklacara@mac.com>
Subject: Re: release status as of 9/12/2004
Date: Tue, 12 Oct 2004 13:12:29 -0700
To: Derby Development <derby-dev@db.apache.org>


On Oct 12, 2004, at 10:52 AM, Samuel Andrew McIntyre wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> On Oct 12, 2004, at 5:12 AM, Dick Applebaum wrote:
>
>> 1) How do you plan to resolve the issue with OS X?
>
> I like Dan's suggestion in the last paragraph here, by turning the  
> feature on only if we know we're running a JVM by a vendor where it  
> has been certified to work:
>
> http://nagoya.apache.org/eyebrowse/ReadMsg?listName=derby- 
> user@db.apache.org&msgNo=139
>
> Mike and/or Suresh would have a better idea than I where it would be  
> appropriate to put such a check.
>

How about just doing a try/catch at start and turning the feature off  
if you get an error?

Dick