On 10/25/2011 8:32 AM, Rick Hillegas (Commented) (JIRA) wrote:
[
https://issues.apache.org/jira/browse/DERBY-5469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13135146#comment-13135146
]
Rick Hillegas commented on DERBY-5469:
--------------------------------------
When I back out the patch and remove the IBM JDK 7 from my Ubuntu appliance
(leaving only the IBM JDK 6), the build fails early on. The build is unable to
find a JDK to build against. Might be an environmental problem in my Linux
appliance. Might be that we have never tested the build against IBM JDKs on
Linux. In any event, I think that fixing the build in this environment falls
outside the scope of this JIRA.
Have we tested the build against IBM JDKs on Linux?
I know there are nightly builds on linux with JDK 1.6, but I think with
the following local.properties:
j16lib=/local1/cloudtst/dev/src/ibm16/jre/lib
j15lib=/local1/cloudtst/dev/src/ibm15/jre/lib
j14lib=/local1/cloudtst/dev/src/ibm142/jre/lib
jdk16=/local1/cloudtst/dev/src/ibm16
java14compile.classpath=${j14lib}/core.jar;${j14lib}/server.jar;${j14lib}/xml.jar;${j14lib}/ibmjcefw.jar;${j14lib}/security.jar
java15compile.classpath=${j15lib}/core.jar;${j15lib}/server.jar;${j15lib}/xml.jar;${j15lib}/ibmjcefw.jar;${j15lib}/security.jar;${j15lib}/vm.jar
java16compile.classpath=${j16lib}/sql.jar;${j16lib}/xml.jar;${j16lib}/ibmjcefw.jar;${j16lib}/rt.jar;${j16lib}/vm.jar;${j16lib}/security.jar;${j16lib}/
java.util.jar;${j16lib}/jndi.jar;${j16lib}/logging.jar;${j16lib}/jlm.jar;${j16lib}/annotation.jar
junit=/local1/cloudtst/dev/src/junit/junit.jar
proceed=true
sane=false
I have built on linux in the past with JDK 1.6 as well, but have always
set the various compile.classpath properties.
