[
https://issues.apache.org/jira/browse/MRESOLVER-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926384#comment-17926384
]
Elliotte Rusty Harold commented on MRESOLVER-671:
-------------------------------------------------
And let me just quote what I said in the thread you cite:
I think that's likely to produce far more weird, hard-to-debug
breakages of Maven on end users' machines. IMHO we are already far too
aggressive in what we consider supported. The enterprise and big tech
world simply does not upgrade that fast. For instance, 3.5.0 is what I
had on my day job machine because that's what the package manager
installs in 2023, not because it's the version I picked.
There is a clear distinction between Maven itself and the plugins and
libraries pulled in via a pom.xml. Maven is a tool installed on end
users machines and is years out of date in many cases. Libraries
published for consumption by builds through declarations in the
pom.xml, and this includes plugins, should not be tightly coupled to
the versions of tools installed on end user systems such as mvn and
the JDK. It's the robustness principle in action, be conservative in
what you send, be liberal in what you accept.
> 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)
