[
https://issues.apache.org/jira/browse/MNG-7501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17557004#comment-17557004
]
ASF GitHub Bot commented on MNG-7501:
-------------------------------------
rmannibucau commented on PR #756:
URL: https://github.com/apache/maven/pull/756#issuecomment-1161988690
> drop pom.xml: are we so constrained that we start complexifying?
Guess that to be fair it should be asked both ways, is current verbosity
worth it and holding any information? Less is printed better it is IMHO and
complexity is quite relative so think so personally.
> mono-module: ok, we can do it, but does it deserve special case?
Don't think so since the same issue hits big multimodule projects.
> debug mode: it defeats the intent = have useful info on normal run (if we
run debug mode, we're already lost in details)
it is no more true since we get logger configuration on the CLI so we have
built-in toggles now :)
> "Generally speaking module name should be sufficient if dev did it
right.": no, definitely no, if you have 5 levels of directories and you put
them in the module name, you're lost
Hmm, do you have some examples? Took tomee, activemq, cxf, camel and it is
not the case and it is already complex enough projects IMHO.
The side note there can be that all this implementation assumes using a
single thread so can not even solve the original use case (this is where I
mentionned putting it per line in compressed form).
> display relative path to pom.xml
> --------------------------------
>
> Key: MNG-7501
> URL: https://issues.apache.org/jira/browse/MNG-7501
> Project: Maven
> Issue Type: Improvement
> Components: Command Line
> Affects Versions: 3.8.6
> Reporter: Herve Boutemy
> Priority: Major
> Fix For: 3.9.0-candidate
>
>
> when building large multi-module project, when a failure happens in the
> middle of the build, it's not easy to even identify where the module is
> located in the source tree: Maven displays the module name, but not the path
> to pom.xml. Then often we have to read output log of goals that have run
> hoping to find a hint
> it would be nice to have by default the path to the pom.xml displayed during
> Maven run.
> I see 2 options:
> 1. either in the module build header:
> {noformat}
> [INFO] --< org.apache.maven.its.plugins:maven-it-plugin-dependency-resolution
> >--
> [INFO] Building Maven IT Plugin :: Dependency Resolution 2.1-SNAPSHOT
> [31/78]
> [INFO]
> core-it-support/core-it-plugins/maven-it-plugin-dependency-resolution/pom.xml
> [INFO] ----------------------------[ maven-plugin
> ]----------------------------
> {noformat}
> 2. or in each goal execution line during the module build:
> {noformat}
> [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @
> maven-it-plugin-dependency-resolution
> core-it-support/core-it-plugins/maven-it-plugin-dependency-resolution/pom.xml
> ---
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
