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 2024/10/15 07:47:00 UTC

[jira] [Commented] (MARTIFACT-74) describe build groupId

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

Michael Osipov commented on MARTIFACT-74:
-----------------------------------------

We have a similiar approach in Maven Core for the build thread ID. [~kwin], added code to drop group ID if it never changes, but add it if it does. Do you need reference?

> describe build groupId
> ----------------------
>
>                 Key: MARTIFACT-74
>                 URL: https://issues.apache.org/jira/browse/MARTIFACT-74
>             Project: Maven Artifact Plugin
>          Issue Type: New Feature
>          Components: artifact:describe-build-output (experimental)
>    Affects Versions: 3.5.2
>            Reporter: Herve Boutemy
>            Priority: Major
>             Fix For: 3.5.3
>
>
> groupId has been dropped from output of describe-build-output because it takes much output space, with value that is in general quite static: often, groupId is the same for all modules of a build
> but sometimes, this is not the case: it would be useful to prepend the file-level output with a simple analysis for groupId:
> - what groupId(s) is used, and how many modules for each?
> - is there any artifactId that is provided as part of multiple groupId?
> this should be a simple addition, with compact but useful info



--
This message was sent by Atlassian Jira
(v8.20.10#820010)