[
https://issues.apache.org/jira/browse/DERBY-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663116#action_12663116
]
myrna edited comment on DERBY-3989 at 1/12/09 2:13 PM:
--------------------------------------------------------------------
For what it's worth, the compile works correctly wtih the same properties
setting if I'm building with the ibm16 compiler.
In that case, the printCompilerProperties prints out that it's using 1.6:
[echo] Before setting properties: compilerLevel16 = 1.6
and print one extra line in the first call, after 'Setting property
java15compile.classpath to...':
[setJdkProperties] Setting property java16compile.classpath to
<pathto>\ibm16\jre\lib\annotation.jar;<pathto>\ibm16\jre\lib\beans.jar;<pathto>\ibm16\jre\lib\charsets.jar;<pathto>\ibm16\jre\lib\deploy.jar;<pathto>\ibm16\jre\lib\ibmcertpathfw.jar;<pathto>\ibm16\jre\lib\ibmcertpathprovider.jar;<pathto>\ibm16\jre\lib\ibmcfw.jar;<pathto>\ibm16\jre\lib\ibmjcefw.jar;<pathto>\ibm16\jre\lib\ibmjgssfw.jar;<pathto>\ibm16\jre\lib\ibmjgssprovider.jar;<pathto>\ibm16\jre\lib\ibmjssefw.jar;<pathto>\ibm16\jre\lib\ibmjsseprovider2.jar;<pathto>\ibm16\jre\lib\ibmorb.jar;<pathto>\ibm16\jre\lib\ibmorbapi.jar;<pathto>\ibm16\jre\lib\ibmpkcs.jar;<pathto>\ibm16\jre\lib\ibmsaslfw.jar;<pathto>\ibm16\jre\lib\ibmxmlcrypto.jar;<pathto>\ibm16\jre\lib\j9zip.jar;<pathto>\ibm16\jre\lib\java.util.jar;<pathto>\ibm16\jre\lib\javascript.jar;<pathto>\ibm16\jre\lib\javaws.jar;<pathto>\ibm16\jre\lib\jlm.jar;<pathto>\ibm16\jre\lib\jndi.jar;<pathto>\ibm16\jre\lib\logging.jar;<pathto>\ibm16\jre\lib\management-agent.jar;<pathto>\ibm16\jre\lib\plugin.jar;<pathto>\ibm16\jre\lib\resources.jar;<pathto>\ibm16\jre\lib\rt.jar;<pathto>\ibm16\jre\lib\security.jar;<pathto>\ibm16\jre\lib\sql.jar;<pathto>\ibm16\jre\lib\vm.jar;<pathto>\ibm16\jre\lib\xml.jar;<pathto>\ibm16\jre\lib\xmldsigfw.jar
was (Author: myrna):
For what it's worth, the compile works correctly wtih the same properties
setting if I'm building with the ibm16 compiler.
> Set the Java 5 compilation path based on the Java 6 compilation path if a
> Java 5 environment can't be found but a Java 6 environment can be
> -------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3989
> URL: https://issues.apache.org/jira/browse/DERBY-3989
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.5.0.0
> Reporter: Rick Hillegas
> Attachments: derby-3989-01-aa-optionalJava5.diff,
> derby-3989-01-ab-optionalJava5.diff
>
>
> This will make the build even more flexible. Probably involves the following
> changes:
> 1) Relaxing the requirement in PropertySetter that a Java 5 JDK must exist
> 2) Having PropertySetter look for a Java 6 JDK (and set
> java16compile.classpath accordingly) just as PropertySetter looks for a Java
> 5 JDK today
> 3) Changing the setCompilerProperties target in the master build script so
> that it
> a) requires that java15compile.classpath or java16compile.classpath is set
> (it's ok for both to be set)
> b) sets java15compile.classpath to ${jdbc3stubs}:${java16compile.classpath}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
