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: local policy)
Date: Mon, 19 Jun 2006 09:10:40 -0700
From: Rick Hillegas <Richard.Hillegas@Sun.COM>
Subject: Re: [jira] Commented: (DERBY-930) Add support for autoloading of
 Derby
 client drivers
In-reply-to: <4496BFBC.4090002@amberpoint.com>
Sender: Richard.Hillegas@Sun.COM
To: derby-dev@db.apache.org
Message-id: <4496CC80.80608@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=UTF-8
Content-transfer-encoding: 7BIT
References: <22929314.1150729470667.JavaMail.jira@brutus>
 <4496BFBC.4090002@amberpoint.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)

Hi Bryan,

Thanks for the quick response. I have revised the release note. 
Hopefully, it now describes the VM-specific issues better.

Regards,
-Rick

Bryan Pendleton wrote:

> Rick Hillegas (JIRA) wrote:
>
>> Adding a release note for this issue:
>
>
> Hi Rick, thanks for writing the release note.
>
> It wasn't clear to me from reading the release note whether this issue
> only affects JDK 1.6 environments, or whether it can arise under older
> VMs as well.
>
> If it only affects JDK 1.6 environments, perhaps we could change the
> release note to read:
>
>   If an embedded Derby application runs in a JDK 1.6/JDBC4 environment,
>   and generates its own Derby properties on the fly, and...
>
> thanks,
>
> bryan
>
>