db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren" <m.v.lunte...@gmail.com>
Subject Re: Change to Derby build soon
Date Mon, 17 Dec 2007 18:40:55 GMT
On 12/17/07, Rick Hillegas <Richard.Hillegas@sun.com> wrote:
> Unless someone objects, tomorrow I would like to change the Derby build
> so that, by default, the build will try to automatically set the
> compiler properties if they are not already set in ant.properties. I
> checked in this behavior a month ago, but right now you have to opt into
> this behavior by setting the autosetProps flag. Tomorrow I would like to
> change the build so that instead of opting into this behavior, you will
> get it by default--of course, you will be able to opt out if necessary.
> After making this change, the Derby build will behave this way:
> 1) If ant.properties is empty, then the build will try to set the
> compiler properties based on your platform and vm vendor.
> 2) If this breaks the build for you, then you can get the old behavior
> by setting a new flag in your ant.properties: dontAutosetProps.
> Regards,
> -Rick

If I understand this correctly, we'll now have 2 flags,
dontAutosetProps and setAutoProps?

Why not have one?


View raw message