[
https://issues.apache.org/jira/browse/DERBY-3966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12656124#action_12656124
]
Rick Hillegas commented on DERBY-3966:
--------------------------------------
Thanks for replying, Knut.
I see your point about wanting to use Java 6 features. I think we are caught
between two goals here:
1) the desire to compile the entire Derby system out-of-the-box
2) the desire to capitalize on improvements made in later releases of the VM
Until we can require that developers have a Java 6 compiler, I think that
satifying (2) may introduce some ugliness (e.g., more stubs). I'm not happy
about that, but I could live with it in order to satisfy (1).
> 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, derby-3966-05-aa-notice.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.
