You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2022/01/05 21:08:00 UTC

[jira] [Commented] (MNG-7381) Parallel builder should use a shorter thread name

    [ https://issues.apache.org/jira/browse/MNG-7381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17469550#comment-17469550 ] 

Michael Osipov commented on MNG-7381:
-------------------------------------

I consider type and version unnecessary 

> Parallel builder should use a shorter thread name
> -------------------------------------------------
>
>                 Key: MNG-7381
>                 URL: https://issues.apache.org/jira/browse/MNG-7381
>             Project: Maven
>          Issue Type: Improvement
>    Affects Versions: 3.8.2, 3.8.3, 3.8.4
>            Reporter: Falko Modler
>            Priority: Minor
>
> Following up on MNG-6471, the thread name that is now generated can easily exceed 60 chars or more, e.g.:
> {noformat}
> [mvn-builder-de.somecorp.foo.barbazx:register-server:jar:2.0.0.local-dev3] ...
> {noformat}
> This devaluates {{-Dorg.slf4j.simpleLogger.showThreadName=true}} as the only easily availble option to differentiate where a logline comes from.
> As discussed [here|https://github.com/apache/maven/pull/177#issuecomment-1005975037] (and in the following comments), one idea is to make the pattern configurable (or simpler, have a toggle to include the entire module id or only its artifactId).
> A slightly different approach could try to detect whether there are "duplicate" artifactIds in the reactor and only append the groupId for those.
> In any way, type, classfier and version don't seem to add anything valuable.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)