vy commented on issue #85: URL: https://github.com/apache/logging-log4j-tools/issues/85#issuecomment-1816470954
Could you elabore it a bit more, please? Consider the following plugin executions: ``` [INFO] --- clean:3.2.0:clean (default-clean) @ log4j-changelog-maven-plugin --- [INFO] Deleting /home/vy/Projects/log4j-tools/log4j-changelog-maven-plugin/target [INFO] [INFO] --- flatten:1.5.0:clean (clean-flattened-pom) @ log4j-changelog-maven-plugin --- [INFO] Deleting /home/vy/Projects/log4j-tools/log4j-changelog-maven-plugin/.flattened-pom.xml [INFO] [INFO] --- enforcer:3.3.0:enforce (enforce-upper-bound-deps) @ log4j-changelog-maven-plugin --- [INFO] Rule 0: org.apache.maven.enforcer.rules.dependency.RequireUpperBoundDeps passed [INFO] [INFO] --- remote-resources:3.1.0:process (process-resource-bundles) @ log4j-changelog-maven-plugin --- [INFO] Preparing remote bundle org.apache.apache.resources:apache-jar-resource-bundle:1.5 [INFO] Copying 3 resources from 1 bundle. [INFO] [INFO] --- resources:3.3.1:resources (default-resources) @ log4j-changelog-maven-plugin --- [INFO] skip non existing resourceDirectory /home/vy/Projects/log4j-tools/log4j-changelog-maven-plugin/src/main/resources [INFO] Copying 3 resources from target/maven-shared-archive-resources to target/classes [INFO] [INFO] --- flatten:1.5.0:flatten (flatten-revision) @ log4j-changelog-maven-plugin --- [INFO] Generating flattened POM of project org.apache.logging.log4j:log4j-changelog-maven-plugin:maven-plugin:0.6.0-SNAPSHOT... [INFO] [INFO] --- compiler:3.11.0:compile (default-compile) @ log4j-changelog-maven-plugin --- [INFO] Changes detected - recompiling the module! :dependency [INFO] Compiling 5 source files with javac [debug release 8] to target/classes ``` All of them display some brief information about what they are doing. Likewise, `log4j-changelog-m-p` states (looking at the log output you shared): 1. It processed 54 release directories and the last one was `C:\tmp\test\src\changelog\2.22.0` – this is good for checking _"Did it really process all my changelog directories?"_ 2. It is exporting the upcoming release to `C:\tmp\test\src\changelog\.2.x.x` – this is good for checking _"Are the release notes ready?"_ These convey information that matters, IMO. `flatten-m-p`, `m-compiler-p`, `m-enforcer-p`, `m-clean-p`, etc. all do the same. Do you think these are irrelevant and should be moved to a lower logging level? -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
