[
https://issues.apache.org/jira/browse/MNG-7438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNG-7438:
-------------------------------
Description:
currently, when running goals/mojos, we have in debug logs
{noformat}
[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
{noformat}
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
{noformat}
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test' execution
'default-test' with basic configurator -->
{noformat}
h2. final debug messages
{noformat}
[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 -->
{noformat}
was:
currently, when running goals/mojos, we have in debug logs
{noformat}
[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
{noformat}
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
{noformat}
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test' execution
'default-test' with basic configurator -->
{noformat}
> add execution id to "Configuring mojo xxx with basic configurator" debug
> message
> --------------------------------------------------------------------------------
>
> Key: MNG-7438
> URL: https://issues.apache.org/jira/browse/MNG-7438
> Project: Maven
> Issue Type: Improvement
> Components: Core
> Affects Versions: 3.8.5
> Reporter: Herve Boutemy
> Assignee: Herve Boutemy
> Priority: Major
> Fix For: 3.9.0
>
>
> currently, when running goals/mojos, we have in debug logs
> {noformat}
> [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
> {noformat}
> 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
> {noformat}
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test' execution
> 'default-test' with basic configurator -->
> {noformat}
> h2. final debug messages
> {noformat}
> [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 -->
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
