Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
3.8.5
-
None
Description
currently, when running goals/mojos, we have in debug logs
[INFO] --- maven-surefire-plugin:3.0.0-M5:test (default-test) @ org.example.apache.maven.execution --- [DEBUG] Configuring mojo org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test from plugin realm ClassRealm[plugin>org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5, parent: sun.misc.Launcher$AppClassLoader@7852e922] [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test' with basic configurator --> [DEBUG] (s) additionalClasspathElements = [] [DEBUG] (s) basedir = /home/herve/tmp/org.example.apache.maven.execution
on the "Configuring mojo 'org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test' with basic configurator" line, it completely hides the fact that configuration is valid for an execution id, that has a default value when nobody defined any (see https://maven.apache.org/guides/mini/guide-default-execution-ids.html )
Just adding "execution 'default-test'" would make things more clear so people learn about execution ids
[DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test' execution 'default-test' with basic configurator -->
final debug messages
[DEBUG] Loading mojo org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test from plugin realm ClassRealm[plugin>org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5, parent: sun.misc.Launcher$AppClassLoader@7852e922] [DEBUG] Configuring mojo execution 'org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test:default-test' with basic configurator -->
Attachments
Issue Links
- links to