PayBas opened a new issue, #879: URL: https://github.com/apache/maven-mvnd/issues/879
http://www.mojohaus.org/properties-maven-plugin/usage.html has a goal called `set-system-properties` which can be used to set (you guessed it) system properties (as opposed to Maven properties) for specific Maven projects. I use it to silence some particularly spammy Maven plugins which don't offer built-in verbosity options: ```xml <build> <plugins> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>properties-maven-plugin</artifactId> <executions> <execution> <goals> <goal>set-system-properties</goal> </goals> <configuration> <properties> <property> <name>org.slf4j.simpleLogger.log.io.swagger.codegen.v3.AbstractGenerator</name> <value>warn</value> </property> <property> <name>org.slf4j.simpleLogger.log.io.swagger.codegen.v3.generators.DefaultCodegenConfig</name> <value>error</value> </property> </properties> </configuration> </execution> </executions> </plugin> </plugins> </build> ``` This works perfectly well with `mvn`, but doesn't work with `mvnd` If I run a build with the `-Dorg.slf4j.simpleLogger.showLogName` parameter, I can see that it's still the same log-producers. So either the system properties aren't applied, or the way `mvnd` collects the logs results in strange behavior. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
