[
https://issues.apache.org/jira/browse/DERBY-3399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567162#action_12567162
]
kmarsden edited comment on DERBY-3399 at 2/8/08 11:04 AM:
----------------------------------------------------------------
To build with IBM 1.6 I have to set:
j16lib=${jdk16}/jre/lib
java16compile.classpath=${j16lib}/sql.jar;${j16lib}/xml.jar;${j16lib}/ibmjcefw.jar;${j16lib}/security.jar;${j16lib}/rt.jar;${j16lib}/security.jar;${j16lib}/vm.jar;${j16lib}/security.jar;${j16lib}/java.util.jar;${j16lib}/jndi.jar
was (Author: kmarsden):
To build with IBM 1.6 I have to set:
java16compile.classpath=${j16lib}/sql.jar;${j16lib}/xml.jar;${j16lib}/ibmjcefw.jar;${j16lib}/security.jar;${j16lib}/rt.jar;${j16lib}/security.jar;${j16lib}/vm.jar;${j16lib}/security.jar;${j16lib}/java.util.jar;${j16lib}/jndi.jar
> The automatic compile path property setting for the build system should be
> expanded to handle Java SE 6 virtual machines.
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3399
> URL: https://issues.apache.org/jira/browse/DERBY-3399
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Reporter: Daniel John Debrunner
> Priority: Minor
>
> Setting jdk16 in my ant.properties to IBM's JavaSE 6.0 JDK does not produce a
> successful build.
> I think the issue is that this line in compilepath.properties is specific to
> Sun's Java SE implementation.
> java16compile.classpath=${j16lib}/rt.jar
> IBM's vms require more jars from the JRE lib folder.
> Does the property setter automatically add all jars into the classpath?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
