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: Thu, 10 Aug 2006 14:00:15 -0700
From: Rick Hillegas <Richard.Hillegas@Sun.COM>
Subject: Re: build setup for releases
In-reply-to: <44DB9B85.8010002@apache.org>
Sender: Richard.Hillegas@Sun.COM
To: derby-dev@db.apache.org
Message-id: <44DB9E5F.8000403@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
References: <44DB9B85.8010002@apache.org>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)

I think this would be very useful. Where should we put this information?

And another question: At this point, my builds create the following 
optional artifacts:

1) The JDBC4 support.
2) The osgi support class EmbeddedActivator
3) The jsr169 support

Are there any other optional artifacts which I should build?

Thanks,
-Rick

Daniel John Debrunner wrote:

>In the previous releases has their been documentation about how the jars
>were built? I've never seen any, but I've never looked for it. Seems
>like it would be useful for resolving any strange bugs later that are
>compiler/environment related. Something like:
>
>os platform - linux
>java compiler(s) - Sun 1.4
>jdk 1.3 environment - Sun 1.3.1
>jdk 1.4 environment - Sun 1.4.2
>jdk 1.6 environment - Sun Mustang beta
>jsr 169 env - WCTME 5.7
>OSGi jar - OSGI download
>
>etc.
>
>Dan.
>
>  
>