db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3966) 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
Date Fri, 12 Dec 2008 16:36:45 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12656052#action_12656052
] 

Rick Hillegas commented on DERBY-3966:
--------------------------------------

Thanks for the quick feedback, Knut. And thanks to Bryan for the vote of confidence on the
dev list.

I am not a lawyer. Ahem and further throat clearing. But after re-reading the first couple
sections of the Apache 2.0 license, I am concerned that we are not properly attributing the
Xalan jars which we're already using. It seems to me that the jar files are an Object form
of the original Xalan Work. Since we re-distribute this Xalan Work, we should include the
Xalan NOTICE in our Derby NOTICE file just as we include the Harmony NOTICE.

Concerning java15compile.classpath: I agree that we should do what you suggest. But I think
that should be a separate JIRA. Right now BUILDING.txt says that you have to have a Java 5
JDK on your machine and this requirement is enforced by PropertySetter. I agree that we ought
to be able to remove that requirement now that we include the JDBC3 stubs, provided that the
machine has a Java 6 JDK.

Maybe as part of that JIRA (or another JIRA), we should set java16compile.classpath and jdk16
either by looking for the Java 6 JDK in the file system or by setting it equal to ${jdbc4stubs}:${java15compile.classpath}.
Then we would have a pretty flexible build which compiles all of Derby from Derby source provided
that you have a Java 5 or greater JDK on your machine.

What do you think? I will log the additional JIRAs if you agree that this is the right approach.

Thanks.

> 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.


Mime
View raw message