We are exploring a parallel, separate maintenance model for newer JDK versions, which will not affect the upstream main branch policy at all.
The core idea is:
1：The upstream project continues normal development with Java 8 as baseline
2：We maintain independent adaptation branches for newer JDK versions (Java 17+, etc.)
3：These branches serve users who need to run or build under modern Java environments
We have noticed community demand for newer‑JDK compatibility, and have started JDK upgrade adaptations for several open‑source projects.
If there is ongoing community interest, we are willing to long‑term maintain 2–3 JDK‑upgraded variant branches independently.
The related PR is an exploration of this optional maintenance solution, rather than changing the official Java baseline policy of sqlite‑jdbc.
We welcome community discussion on this idea.
We are exploring a parallel, separate maintenance model for newer JDK versions, which will not affect the upstream main branch policy at all.
The core idea is:
1：The upstream project continues normal development with Java 8 as baseline
2：We maintain independent adaptation branches for newer JDK versions (Java 17+, etc.)
3：These branches serve users who need to run or build under modern Java environments
We have noticed community demand for newer‑JDK compatibility, and have started JDK upgrade adaptations for several open‑source projects.
If there is ongoing community interest, we are willing to long‑term maintain 2–3 JDK‑upgraded variant branches independently.
The related PR is an exploration of this optional maintenance solution, rather than changing the official Java baseline policy of sqlite‑jdbc.
We welcome community discussion on this idea.