[
https://issues.apache.org/jira/browse/DERBY-3966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12656041#action_12656041
]
Knut Anders Hatlen commented on DERBY-3966:
-------------------------------------------
I have verified that java14compile.classpath is set to
java15compile.classpath+xalan+serializer if JDK 1.4 cannot be found, and that
it uses the j14lib property if it's set. So unless there's something we need to
update in the NOTICE file because of the added jar files (I don't think so
since we already include other jars from Xalan) I think this patch is ready for
commit.
Next step is to set java15compile.classpath automatically based on
stubs+java16compile.classpath if JDK 5 cannot be found?
> 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.
