[
https://issues.apache.org/jira/browse/MARTIFACT-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17891419#comment-17891419
]
Herve Boutemy commented on MARTIFACT-74:
----------------------------------------
yes, groupId is useful: just not on every artifact, because it's mostly the
same value everywhere
see
https://github.com/jvm-repo-rebuild/reproducible-central/actions/runs/11415857110/job/31766378601?pr=437#step:7:2375
> 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)
