[
https://issues.apache.org/jira/browse/DERBY-6857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134962#comment-15134962
]
ASF subversion and git services commented on DERBY-6857:
--------------------------------------------------------
Commit 1728732 from [~knutanders] in branch 'code/trunk'
[ https://svn.apache.org/r1728732 ]
DERBY-6857: Deprecate support for building Derby under JDKs 6 and 7
Make ClassInvestigator understand the new byte codes added in Java 7
to support InvokeDynamic and lambda. Also transform an inner class to
a lambda in the NetworkServerControl class to test that
ClassInvestigator understands the new codes.
> Deprecate support for building Derby under JDKs 6 and 7
> -------------------------------------------------------
>
> Key: DERBY-6857
> URL: https://issues.apache.org/jira/browse/DERBY-6857
> Project: Derby
> Issue Type: Bug
> Components: Build tools
> Affects Versions: 10.13.0.0
> Reporter: Rick Hillegas
> Attachments: ClassReferenceReader.java, Windows-sane-TypeId.class,
> classReferenceComparison.txt, derby-6857-01-aa-remove6and7.diff,
> derby-6857-02-aa-cleanupOldJdks.diff, derby-6857-03-aa-minimumVersion.diff,
> derby-6857-04-aa-pruneConstantClasses.diff, jardriftcheck.diff,
> mac-derby-jar-verbose.txt, mac-sane-TypeId.class, new-byte-codes.diff,
> windows-derby-jar-verbose.txt
>
>
> The community voted to stop supporting Java 6 and 7 as of release 10.13. See
> the 2015-09-12 entry here: http://wiki.apache.org/db-derby/VoteResults. We no
> longer need to support building Derby with those JDKs. This issue tracks
> changes needed to remove that support and simplify the build.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
