Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
Date: Mon, 19 Nov 2007 06:13:14 -0800
From: Rick Hillegas <Richard.Hillegas@Sun.COM>
Subject: Automatic setting of compiler classpath properties at build time
Sender: Richard.Hillegas@Sun.COM
To: derby-dev@db.apache.org
Message-id: <474199FA.9030800@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728)

I have checked in some build logic which automatically sets the compiler 
classpath properties. This is part of the work on DERBY-3117 and the 
goal,  ultimately, is to have a Derby build script which works out of 
the box without any customizing of ant.properties.

In order to take advantage of this automatic property setting today, you 
need to remove some existing properties from your ant.properties 
(j14lib, j15lib, java14compile.classpath, java15compile.classpath) and, 
instead, set the following in ant.properties:

autosetProps=on

That is, right now you have to request the automatic setting of 
properties. A month from now, I would like to make automatic property 
setting the default. Note that even after automatic property setting 
becomes the default, you will still be able to override the defaults by 
setting the properties as you do today.

Over the next month, I would appreciate it if people could try out the 
automatic property setting in their own environments and let me know if 
something breaks. I would like this to be as solid as possible before 
switching the default behavior.

Thanks,
-Rick