[
https://issues.apache.org/jira/browse/MRESOLVER-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926388#comment-17926388
]
Tamas Cservenak commented on MRESOLVER-671:
-------------------------------------------
I think you are conflating things here. I really understand that some companies
have very conservative stance regarding their tools, but also you should
understand that others do not. Moreover, this is an open source project, so
unsure why should we apply anyones policy to it, nor am unsure why do you
expect that same toolset you use or used in some company "should work" for this
project as well (like "it must work as I used this on my work too"). Don't
conflate your daily work and your OSS contribution, that's all.
In fact, some devs really think about this whole project "as if it would be a
company". Well, it is not. We have no managers, no schedules, no trainees nor
secretaries and so on and so on. Do not bring your working habits here, and
especially do not try to force them on others. And this is not only about
toolset you want to use, but also general remark about using forks or not,
polluting canonical repository with private branches (named in such way, to not
reveal any clue what it is about, or issue it tries to fix), etc. I understand
the "this is how i used to work at ACME Corp" sentiment, but please understand:
this is not ACME Corp.
> 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)
