You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Guillaume Nodet (Jira)" <ji...@apache.org> on 2022/10/20 08:11:03 UTC

[jira] [Updated] (MNG-7381) Shorten parallel builder thread name to artifactId, conditionally with groupId

     [ https://issues.apache.org/jira/browse/MNG-7381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guillaume Nodet updated MNG-7381:
---------------------------------
    Fix Version/s: 4.0.0-alpha-2

> Shorten parallel builder thread name to artifactId, conditionally with groupId
> ------------------------------------------------------------------------------
>
>                 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
>            Assignee: Michael Osipov
>            Priority: Minor
>             Fix For: 3.8.5, 4.0.0-alpha-1, 4.0.0-alpha-2, 4.0.0
>
>
> 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.10#820010)