[
https://issues.apache.org/jira/browse/MRESOLVER-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17925796#comment-17925796
]
Elliotte Rusty Harold edited comment on MRESOLVER-671 at 2/11/25 11:45 AM:
---------------------------------------------------------------------------
I rarely use the latest OS. I rarely use the latest Java. And wrt Java that's
the posture of the vast majority of organizations I've ever encountered, Meta
and Google included. The devs I notice using the latest LTS JDK are individual
cowboy developers. The large organizations where most developers work most of
the time do not run or build with the latest LTS.
I no longer have access to the current statistics Google collects about what
its customers want (a broader and more accurate sample than I've seen
elsewhere) but when I did the pattern was clear. The latest LTS was extremely
rare. Second to latest was present but not the majority. Third latest was
probably a plurality, and there was a long and thick tail of older versions.
Non-LTS releases were a drop in the bucket except for JDKs before LTS was a
thing (i.e. Java 1.7 and earlier) and these we saw a shocking number of.
was (Author: elharo):
I rarely use the latest OS. I rarely use the latest Java. And wrt Java that's
the posture of the vast majority of organizations I've ever encountered, Meta
and Google included. The devs I notice using the latest LTS JDK are individual
cowboy developers. The large organizations where most developers work most of
the time do not run or build with the latest LTS.
I no longer have access to the current statistics Google collects about what
its customers want (a broader and more accurate sample than I've seen
elsewhere) but when I did the pattern was clear. The latest LTS was extremely
rare. Second to latest was present but not the majority. Third latest was
probably a plurality, and there was a long and thick tail of older versions.
> 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)
