[
https://issues.apache.org/jira/browse/MRESOLVER-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17940641#comment-17940641
]
Tamas Cservenak commented on MRESOLVER-671:
-------------------------------------------
Resolver (as a project) is a just half of the story, as you know, resolver is
"incomplete" as well (is being completed by components implemented in Maven)
and is _also_ tested in Maven UTs and ITs. This will become clearer once we
merge Resolver into Maven (5-ish?). Maven 3 introduced Resolver as separate
(and kinda reusable) library, an experiment that never got traction, as
Resolver was not quite (re)used as library as doing that was hard, hence MIMA
[https://github.com/maveniverse/mima]
All in all, Resolver "alone" is not something usable, it needs to be integrated
(and completed by) something, and right now, it is only Maven doing this. So,
while Resolver matrix may not be the case, when you consider resolver + maven
matrixes, it does complete what I wrote above.
> 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)
