[
https://issues.apache.org/jira/browse/MRESOLVER-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926383#comment-17926383
]
Elliotte Rusty Harold commented on MRESOLVER-671:
-------------------------------------------------
It's not just my MacBook. It's every MacBook and Linux system at Google, and
Meta, and many other places with developers who are willing and able to
contribute to Maven. It's the internal build systems that bulld all the open
source from scratch.
Large organizations standardize tooling including the JDK for good reason.
Setting up separate tool paths for external and internal development is a
major inconvenience.
The bad reflex I see is that newer JDKs are better. That's an unproven
assertion. It often isn't true. There've been some nice additions to the
libraries, and a lot in the runtime, but these are counter-balanced by some
actively bad additions to the language.
> 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)
