Myrna van Lunteren wrote:
On 12/17/07, Rick Hillegas <[EMAIL PROTECTED]> 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
Rick,
If I understand this correctly, we'll now have 2 flags,
dontAutosetProps and setAutoProps?
Why not have one?
Myrna
Hi Myrna,
Sorry to create confusion. I am going to remove setAutoProps, introduce
dontAutosetProps, and reverse the sense of the conditionals which
currently inspect setAutoProps. So there will just be one flag, namely,
dontAutosetProps.
Hope this is more clear.
-Rick
