[
https://issues.apache.org/jira/browse/MRESOLVER-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926399#comment-17926399
]
Tamas Cservenak commented on MRESOLVER-671:
-------------------------------------------
Ok, so just to clarify, I am not gonna give up on requiring latest LTS Java
requirements for some builds (if I am asked, I'd do this in Maven Parent, so
for all of them). And the reason for that is well documented in this thread:
there was a vote, that was completely derailed, postponed, and as it turns out,
it happened for nothing: one committer used ancient Java while trying to verify
the build and yelled wolf. I have no time (or better, am not willing to
sacrifice any of my time) to deal with supporting and figuring out the reason
why they vote -1 on a release, as it just create noise and confusion. After
this event, I decided and implemented the enforcer thing in Resolver, for one
purpose: to make sure that _whoever_ tries to build the project (for example as
part of verifying before vote) use pretty much same (or at least "closely
same") tools. As regarding _testing on target Java_ (that is 8 in this case),
both, Resolver and Maven itself CI contain Java 8 in matrix.
> 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)
