[
https://issues.apache.org/jira/browse/DERBY-6857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15120631#comment-15120631
]
Bryan Pendleton commented on DERBY-6857:
----------------------------------------
Concretely, will DRDAConstants.class be present in derby.jar? Or not?
And will this affect the way that we "seal" the jars?
I remember that when I worked on the refactoring of the error message
utility classes last summer (see DERBY-6801, etc.), there was a lot of
finicky little details about which classes were "sealed" in which jars.
Is the ClassLister behavior related to the sealing behavior? I guess that's
what I'm asking.
I can't disagree with any of your analysis so far, it all seems thoroughly
sound and clear.
And I also, unfortunately, have no theories about why the Windows compiler is
acting differently than the compilers on the Mac and on Linux.
I'm fine with your proposed change to ClassLister; let me know if there's
anything I can do to help.
> 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,
> 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)
