[
https://issues.apache.org/jira/browse/MRESOLVER-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17925995#comment-17925995
]
Tamas Cservenak commented on MRESOLVER-671:
-------------------------------------------
I find so many self contradicting things... who are "users" that are forced on
upgrades? You?
I disagree about the "high bar" as well, why you insist on living in past?
Maven4 is not yet even released (GA), and when it MAY be released, we MAY have
already the next Java LTS out.
And you want to go backwards?
In fact, I see folks like you the problem: if all users would use "latest" LTS
(assume they would somehow manage to get it installed), we'd not have issues
that we currently have, to support building projects on wildly different Java
versions, from Java 8 to Java 21, spotless comes to my mind, just to mention
one issue.
Remember this?
https://lists.apache.org/thread/ors31h7cbn6q777f8j9nkzp8x3p0b4nf
> 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)
