[
https://issues.apache.org/jira/browse/DERBY-6857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15122661#comment-15122661
]
Rick Hillegas commented on DERBY-6857:
--------------------------------------
This means that DRDAConstants and friends will NOT appear in the Derby jar
files. So it should cause your Windows builds to once again agree with the
checked-in rosters of jar-file contents. I can imagine that there might be
sealing problems if one of these files of constants leaked into multiple jar
files--which I think is what you are seeing.
I will need your help to verify that the build works smoothly for you on
Windows after I check in the improvement to classlister. Thanks!
> 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)
