[
https://issues.apache.org/jira/browse/MRESOLVER-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17925972#comment-17925972
]
Elliotte Rusty Harold commented on MRESOLVER-671:
-------------------------------------------------
Also, w.r.t the bleeding edge, I think there's an industry-wide failure to
calculate and sum the cost of forcing upgrades on users. It's an externality.
Hardly unique to Maven or Java. As one example, yesterday I blew an hour trying
to install JDK 21 on my laptop just to build the resolver. I still don't have a
working JDK 21 installed, but somehow ended up with JDK 23. No idea how that
happened, but it seems to work so I stopped. Still doesn't work in IntelliJ
though. Fixing that would probably cost another hour.
> 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)
