[
https://issues.apache.org/jira/browse/XERCESJ-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18039609#comment-18039609
]
Elliotte Rusty Harold commented on XERCESJ-1789:
------------------------------------------------
still thinking about this but my gut is that the next point release should
probably still support Java 1.7 to cover existing legacy users. Then we can
discuss a minor or major release that moves to 1.8
> 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)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
