[
https://issues.apache.org/jira/browse/DERBY-3966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-3966:
---------------------------------
Attachment: derby-3966-04-aa-missingJDK14.diff
Attaching derby-3966-04-aa-missingJDK14.diff. This patch makes the 1.4 JDK
optional for a Derby build. I have tested the build on Mac OS X and Ubuntu with
various settings of environment variables and both hiding and including the 1.4
JDKs on those platforms. I would appreciate it if other people could test-drive
the build with this patch on other platforms which we know the community uses,
including Solaris and IBM platforms.
This patch makes the following changes:
1) Adds two new jars from release 2.7.1 of the Apache Xalan project: xalan.jar
and serializer.jar.
2) Changes PropertySetter to not abort the build if the 1.4 JDK is missing.
3) Changes the build to set java14compile.classpath to
${java15compile.classpath}:${xalan}:${serializer} if java14compile.classpath is
not already set. Also prints out the classpath settings if you put
"printCompilerProperties=true" into your ant.properties.
4) Changes JDBC.java, in the test harness, so that the haveClass() method
catches all Throwables and not just Exceptions. I tripped across this one
because my environment setup beefs up the classpath with all jar files in
tools/java. Now that xalan.jar and serializer.jar are in that directory, the
haveClass() probes are finding xml classes in org.apache.xalan. Those classes,
on initialization, are trying to fault in classes in javax.xml.transform. This
means that when I try to run regression tests on a small device platform, a
lack-of-functionality probe which used to trigger a ClassNotFoundException is
now triggering a NoClassDefFoundError.
Touches the following files:
A tools/java/serializer.jar
A tools/java/xalan.jar
M tools/ant/properties/extrapath.properties
Changes to support (1).
M java/build/org/apache/derbyPreBuild/PropertySetter.java
Changes to support (2).
M build.xml
Changes to support (3).
M java/testing/org/apache/derbyTesting/junit/JDBC.java
Changes to support (4).
> Do not require JRE 1.4 libraries at compile time since SUN's JDK 1.4 went out
> of support and can be used on JRE 1.4 without any problem
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3966
> URL: https://issues.apache.org/jira/browse/DERBY-3966
> Project: Derby
> Issue Type: Task
> Components: Build tools
> Reporter: Pedro Faundez Gonzalez
> Attachments: derby-3966-01-aa-jdbc3stubs.diff,
> derby-3966-01-ab-jdbc3jdbc4stubs.diff, derby-3966-01-ac-jdbc3jdbc4stubs.diff,
> derby-3966-02-aa-buildTools.diff, derby-3966-03-aa-notice.diff,
> derby-3966-04-aa-missingJDK14.diff
>
>
> In the "JDK 1.4 support" conversation at Derby Users:
> http://www.nabble.com/JDK-1.4-support--td20650279.html
> I made a point that JRE 1.4 should not be required for build since SUN's JRE
> 1.4 went End Of Life.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
