Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <46F41FB0.9030405@amberpoint.com>
Date: Fri, 21 Sep 2007 12:46:56 -0700
From: Bryan Pendleton <bpendleton@amberpoint.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: derby-dev@db.apache.org
Subject: Re: Requiring Java 5 compiler
References: <46EEA838.808@sun.com> <46F4079B.8070000@sun.com>
 <46F4164A.4000606@amberpoint.com> <46F41B91.2010204@sun.com>
In-Reply-To: <46F41B91.2010204@sun.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

> Thanks, Bryan. I was thinking of wiring a check into the "init" target 
> of the top level build.xml. The build would fail if the compiler wasn't 
> advanced enough. Would that satisfy your build requirements?

Sure, that sounds good!

I'm thinking out loud here, but my expectation is that, once you've
made your change, the impact on me ("Average Joe Derby Developer") is:

  - I have to install Java 1.5 on my machine if I haven't already
  - I have to add the line
        j15lib=/path/to/java1.5/jre/lib
    into my ant.properties
  - I can continue using the same ant.properties for all my 10.2, 10.3,
    and trunk builds
  - I use the same build commands (ant clobber/all/buildjars/junitreport/etc)
    that I currently use
  - If I do either of the first two steps wrong, I get a friendly message.

Is that more or less the way you envision this? If so, sounds fine to me!

thanks,

bryan