Hi there !
I currently configure ktlint with Maven Antrun Plugin as explained there : https://pinterest.github.io/ktlint/install/integrations/ (and it's working like a charm). During the migration of our micro-services to Java 17, I've added the additional JVM args to the Antrun Plugin configuration (as documented).
<jvmarg value="--add-opens"/>
<jvmarg value="java.base/java.lang=ALL-UNNAMED"/>
Your plugin is very interesting for me as it could simplify the linter configuration, but the solution you propose for Java 17 does not fit my need : I have/want to factorize everything related to plugins, in other words plugin management, in my parent POM.
So, is there a way to achieve that regarding Java 17 with your plugin ? If not, is it planned to add some configuration to your plugin to activate these Java 17 flags ? Because adding the .mvn/jvm.config file in all parent depending projects is not an option.
Thank you for you reply !
Hi there !
I currently configure ktlint with Maven Antrun Plugin as explained there : https://pinterest.github.io/ktlint/install/integrations/ (and it's working like a charm). During the migration of our micro-services to Java 17, I've added the additional JVM args to the Antrun Plugin configuration (as documented).
<jvmarg value="--add-opens"/><jvmarg value="java.base/java.lang=ALL-UNNAMED"/>Your plugin is very interesting for me as it could simplify the linter configuration, but the solution you propose for Java 17 does not fit my need : I have/want to factorize everything related to plugins, in other words plugin management, in my parent POM.
So, is there a way to achieve that regarding Java 17 with your plugin ? If not, is it planned to add some configuration to your plugin to activate these Java 17 flags ? Because adding the
.mvn/jvm.configfile in all parent depending projects is not an option.Thank you for you reply !