[jira] [Comment Edited] (XERCESJ-1789) Mix of Java 1.7 and 1.8
"Elliotte Rusty Harold (Jira)" <[email protected]> Wed, 19 Nov 2025 22:17:00 +0000 (UTC)
| Newsgroups | gmane.text.xml.xerces-j.devel |
|---|---|
| Message-ID | <[email protected]> |
[ https://issues.apache.org/jira/browse/XERCESJ-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18039481#comment-18039481 ]
Elliotte Rusty Harold edited comment on XERCESJ-1789 at 11/19/25 10:16 PM:
---------------------------------------------------------------------------
see https://github.com/apache/xerces-j/commit/c11095de326d16962743a64edbaf846ead65fab1
Issue is java.text.Collator
Might be possible to use ICU4J or a hand-rolled collator here instead
was (Author: elharo):
see https://github.com/apache/xerces-j/commit/c11095de326d16962743a64edbaf846ead65fab1
Might be possible to use ICU4J or a hand-rolled collator here instead
> Mix of Java 1.7 and 1.8
> -----------------------
>
> Key: XERCESJ-1789
> URL: https://issues.apache.org/jira/browse/XERCESJ-1789
> Project: Xerces2-J
> Issue Type: Bug
> Reporter: Elliotte Rusty Harold
> Priority: Blocker
>
> Commit c11095d on Jan 23, 2024 drive-by upgraded the build from Java 1.7 to Java 1.8. However, it did not upgrade various other docs and comments, and possibly other things.
> This change should probably be rolled back. Requiring a new major version of Java should not be a casual decision in a PR focused on something else.
> Even if we do decide we want to set Java 1.8 as the minimum for future releases, that needs to be done in its own PR along with updates of all docs and comments that still reference Java 1.7. Furthermore, we'd want at least a minor version, maybe a major version upgrade. This is not something we should do in moving from 2.12.2 to 2.12.3.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)