[
https://issues.apache.org/jira/browse/DERBY-6857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15122803#comment-15122803
]
Bryan Pendleton commented on DERBY-6857:
----------------------------------------
Yes, with the pruneConstantClasses diff applied, I no longer see
the jardriftcheck errors when building jars on my Windows system. Cool!
I'll try running some tests (I don't have the fastest system, sigh), and let
you know
if any runtime errors appear to arise.
But in the meantime, your patch looks good to me.
> 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,
> 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)
