You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
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 !
The text was updated successfully, but these errors were encountered:
You can apply the settings to all projects for a user by adding the arguments in the MAVEN_OPTS environment variable e.g.
add the following to your ~/.profile (if on Unix/Linux):
The only way this Maven plugin could add these arguments would be to fork a new JVM instance, which would make the plugin slower and require a significant amount of code to support. Not having to fork the JVM is the main advantage of using this plugin over the Maven Antrun Plugin. If you'd like to contribute a PR to support an option for forking the JVM, I'd be happy to consider it.
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 !
The text was updated successfully, but these errors were encountered: