[
https://issues.apache.org/jira/browse/DERBY-6857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-6857:
--------------------------------------
Attachment: new-byte-codes.diff
I noticed that the build failed (classlister raised a ClassFormatError) if I
added a lambda expression to the code. It happens because some new byte codes
have been added to the Java class format in the latest releases.
ClassInvestigator doesn't understand those byte codes and raises an error which
makes classlister fail.
The attached patch teaches ClassInvestigator how to handle the new byte codes,
and it transforms an inner class into a lambda expression to verify that it
works.
> 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)
