[
https://issues.apache.org/jira/browse/MRESOLVER-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17925996#comment-17925996
]
Tamas Cservenak edited comment on MRESOLVER-671 at 2/11/25 1:21 PM:
--------------------------------------------------------------------
For me, all this your are for comes from a bad reflex that for some reason
became norm among Maven users (and it seems devs as well):
"you should build the project using the Java version that project targets" (or
in other words, if we build Java 8 stuff, let's use Java 8 to build it).
Corollary:
if you use build a native app that supports Win95, it is expectation to have it
built on Win95.
was (Author: cstamas):
For me, all this your are for comes from a bad reflex that for some reason
became norm among Maven users (and it seems devs as well):
"you should build the project using the Java version that project targets" (or
in other words, if we build Java 8 stuff, let's use Java 8 to build it).
Colloraly:
if you use build a native app that supports Win95, it is expectation to have it
built on Win95.
> 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)
