[
https://issues.apache.org/jira/browse/MRESOLVER-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17925591#comment-17925591
]
Tamas Cservenak commented on MRESOLVER-671:
-------------------------------------------
I disagree, Java 21 is latest LTS (and is not bloody bleeding edge, that would
be 23.0.2 in this moment). Again _build time_ requirement of 'latest LTS' just
makes sense, as every developer I know do have 'latest LTS'.
While Resolver 2.x (output) is said to be Java 8, you have to notice two things:
* Thee is parked https://github.com/apache/maven-resolver/pull/438 (to align
with Maven4)
* Many new functionalities (like JDK transport) are NOT Java 8, but 11+, but
are done as MR JARs to have them work in Java 8 as well (JDK transport in Java
8 just reports "no transport").
* But, I decided to keep Resolver 2.0.x at Java 8 for one reason (and lift Java
to 17+ in 2.1.x or so): having it as such, keeps our options open for Maven
3.10.x with Resolver 2.0.x -- not something I plan, I just like to have options
open if possible.
> Don't require Java 21
> ---------------------
>
> Key: MRESOLVER-671
> URL: https://issues.apache.org/jira/browse/MRESOLVER-671
> Project: Maven Resolver
> Issue Type: Improvement
> Reporter: Elliotte Rusty Harold
> Priority: Major
>
> Apparently maven-resolver now requires Java 21 to build. It won't build even
> with Java 17. This is getting inconveniently out of sync with what devs have
> installed. E.g we can't even jdeprscan for Java 11 or 8 with this version.
> This should be pushed back to 17 or further if possible. The bleeding edge is
> too bloody.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
