You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Herve Boutemy (Jira)" <ji...@apache.org> on 2024/10/21 06:50:00 UTC

[jira] [Comment Edited] (MARTIFACT-74) describe build groupId

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

Herve Boutemy edited comment on MARTIFACT-74 at 10/21/24 6:49 AM:
------------------------------------------------------------------

[~hboutemy], here it is MNG-7381 , have a look.


was (Author: michael-o):
[~hboutemy], here it is, have a look.

> 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
>              Labels: pull-request-available
>             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)