Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
3.0.4
-
None
Description
actually, a lot of Maven output is done with MavenCli logger even 3 times the code executed is not in MavenCli. See the MavenCli code:
1. CLIReportingUtils.showErrors
2. ExecutionEventLogger
3. getBatchTransferListener()
If it can make sense to have the first one reporting with MavenCli logger name, the 2 formers whould better be with their own logger: this would ease filtering
Attachments
Issue Links
- is related to
-
MNG-5395 logger name for plugins should not be DefaultMavenPluginManager
- Closed