Howdy,
See Inline.
On Sun, Feb 4, 2024 at 3:01 PM Elliotte Rusty Harold
wrote:
> I can live with Java 11 if I have to, though I really don't see the
> point. Anything past Java 11 ranges from a major hassle to blocker for
> corporate developers, including those at big tech companies like Meta
FWIW, I work for a large company and our business unit just switched to
Java 17 after eons on Java 8. I think requiring Java 17 or 21 to run Maven
is fine. The existing tooling supports generating Java 8 binaries for those
who need it.
Gary
On Sun, Feb 4, 2024, 9:01 AM Elliotte Rusty Harold
If we're actually voting
+1 for Java 8
-1 for Java 17 or any later version.
I can live with Java 11 if I have to, though I really don't see the
point. Anything past Java 11 ranges from a major hassle to blocker for
corporate developers, including those at big tech companies like Meta
and Google,
If maven itself can (and want) to stick to older java versions, can then
please this one kindly be considered:
https://issues.apache.org/jira/browse/MNG-8040
for example the tycho-maven-plugin (and probably others as well) the
issue is that *dependencies* of the project have moved to higher
