Hi,
On 19.07.22 21:28, Delany wrote:
Elliotte, you make it sound like they don't *want* to upgrade to JDK17. But
who wouldn't want that?
Its usually the business holding that back. If I can tell the business,
sorry, but Maven requires it - then that's the end of the conversation.
They won't argue. Switching to another build system to avoid doing the
inevitable is just making more work.
I made exactly that experience in a project. worked on JDK 8 than
upgrade to JDK 11 (because we had hard requirements)... the same thing
with JDK17 (first completely against upgrade long discussions etc. no
way) after decisions of some frameworks.. simply done within 2 weeks.
Kind regards
Karl Heinz Marbaise
What little I know, I appreciate the bold move to JDK17 and I guess it'll
pay off in the long run. Who knows what's next around the corner.
Regards,
Delany
On Tue, 19 Jul 2022 at 20:39, Elliotte Rusty Harold <elh...@ibiblio.org>
wrote:
On Tue, Jul 19, 2022 at 12:25 PM Karl Heinz Marbaise <khmarba...@gmx.de>
wrote:
Hi to all,
what do you think about using JDK17 as minimum requirement for running
the future Apache Maven 4.0.0 ?
Bluntly, its an atrocious idea that work would likely lead to forks of
maven or a lot of projects abandoning it for other build systems, as well
as many more never upgrading.
Developer preference does not outweigh the needs of the massive installed
base.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
