On Dec 18, 2007 7:19 AM, Rick Hillegas [EMAIL PROTECTED] wrote:
I have checked in this change: subversion revision 605224. Now by
default, the Derby build will try to figure out how to set its compiler
variables, based on your platform and vm. You can override these
defaults by hardcoding your
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
I have checked in this change: subversion revision 605224. Now by
default, the Derby build will try to figure out how to set its compiler
variables, based on your platform and vm. You can override these
defaults by hardcoding your own values for java14compile.classpath and
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
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
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
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
