[
https://jira.codehaus.org/browse/MNG-4859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=276753#comment-276753
]
Falko Modler commented on MNG-4859:
-----------------------------------
This issue of not being able to configure the console output pattern is very
cumbersome when using the parallel build feature of M3.
It would come in very handy, if one could include the thread id in the output
so that the origin of each line is clearly visible.
> Console output pattern should be customizable
> ---------------------------------------------
>
> Key: MNG-4859
> URL: https://jira.codehaus.org/browse/MNG-4859
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Logging
> Affects Versions: 2.2.1, 3.0
> Reporter: Gábor Lipták
>
> http://stackoverflow.com/questions/3890746/maven-output-with-displaying-plugingoalproject-for-each-line-as-prefix/3895261#3895261
> The main idea is, that a lot of plugins produce many console lines. If I look
> for some problem, it is boring and hard to scroll back top see that which
> built project, which plugin, which execution is wrong. It would be real good
> to have some possibility to customize console output like PatternLayout in
> log4j. The following improvements I suggest:
> - leave the possibility to customize severity. For example instead of [INFO]
> [I] would be sufficient.
> - if console log pattern could be defined, colorizing log would be enabled
> http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/PatternLayout.html
> - If you would define thread locals with a map containing project name, id,
> coordinate, running plugin coordinate, execution id, then it would be
> possible to ensure, that no scrolling is needed to see plugin and project.
> Providing aliases could be also enabled. So a console line would look like
> this:
> 2010.01.11 12:33 mygroup:myartifact dependency:resolve[execid] [i] Dependency
> could not be resolved.
> What do you think? Would not it be good?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
