John Embretsen wrote:
Rick Hillegas wrote:
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.
What is the expected behavior when ant.properties is not empty and
does not include the new flag dontAutosetProps? Same as 1)?
Hi John,
Yes, this is the same behavior as (1). Note that in situation (1), you
can hardcode the value of the compiler properties
(java14compile.classpath and java15compile.classpath) in ant.properties.
This will short-circuit the automatic setting of these properties.
Regards,
-Rick
