unclear exceptions from quarkus-maven-plugin 3.8 when used on Java 11 about quarkus

[quarkus-bot]

/cc @quarkusio/devtools (maven)

[gemmellr]

From Zulip chat this was apparently expected/intended for now, because updating quarkus-maven-plugin to targeting Java 17 caused Sisu issues and CI failures even when running on Java 17:

https://quarkusio.zulipchat.com/#narrow/stream/187038-dev/topic/Plugins.20compiled.20for.20Java.2011.20despite.20Quarkus.20requiring.2017.3F/near/426114221

From which it seems that Maven 3.9.6 is required to be used to successfully target Java 17+ for plugins:
https://issues.apache.org/jira/browse/MNG-7913 and
https://quarkusio.zulipchat.com/#narrow/stream/187038-dev/topic/Plugins.20compiled.20for.20Java.2011.20despite.20Quarkus.20requiring.2017.3F/near/426117614

I'll add an enforcer rule to the quickstart I referenced so that folks do get a more obvious error there, albeit it still prints the initial QuarkusBootstrapProvider related problems, it just then wont report the NoSuchElementException but instead explicitly say 'Java 17 or newer is required' instead.

I'll leave this issue open for now for any future improvements (such as going to a 3.9.6 minimum and being able to properly target the plugin to Java 17), and for to help explain things for other users if they hit it.

[alizard0]

Hey folks, I had similar problem with java v11 and quarkus-maven-plugin v3.8.4. The error was : Unable to load the mojo 'generate-code'

After reading your comments, I tried to compile running java 17 and everything worked. Hope it helps someone!