db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kristian Waagan <Kristian.Waa...@Sun.COM>
Subject Heads on for those not using ant.properties for configuring which JDKs to use
Date Fri, 07 Aug 2009 10:05:07 GMT
Hello,

I just committed a patch for DERBY-4263 [1]. This may cause problems, or 
maybe just changes, for some of you that don't use ant.properties to 
configure the JDKs used to build Derby.

If you experience problems, please log a new bug or reopen DERBY-4263.


Thanks,
-- 
Kristian


[1]

Author: kristwaa
Date: Fri Aug  7 09:51:47 2009
New Revision: 801924

URL: http://svn.apache.org/viewvc?rev=801924&view=rev
Log:
DERBY-4263: PropertySetter isn't able to recognize JDK without version number in path.
Added a new algorithm for detecting JDKs on the system. The root search
locations are the same as before, but instead of relying on version numbers in
the JDK directory, jar files and the sub directory structure of the directories
are examined. The new algorithm will try to select JDKs from the same vendor as
the running JVM if possible.
If the new algorithm fails for some reason, the old one will be used.
If both the new and the old algorithm fail, a last attempt will be made by
configuring the build with the running JVM only.

If the more "exotic" approaches are used, a warning message will be printed
to default out. As before, more information can be extracted by setting
printCompilerProperties=true when invoking ant.

Patch file: derby-4263-1b-jdk_detection_by_jars.diff



Mime
View raw message