[
https://issues.apache.org/jira/browse/MNG-7501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17557275#comment-17557275
]
ASF GitHub Bot commented on MNG-7501:
-------------------------------------
cstamas commented on PR #756:
URL: https://github.com/apache/maven/pull/756#issuecomment-1162709496
> @mthmulders and does this impl solves the issue for quarkus? For me it
does not seem so since the printed info is already thread in single threaded
build (plugins already list the folder and quarkus uses default descriptor name
so it is more than sufficient) and in multithreaded builds it looks wrong cause
of the interleaving, so isnt it another example of what I'm explaining?
You mean `mvn -T` builds? As that breaks any log, not only this one. In
general, if you want multi-threaded build, use `mvnd`, as IMHO `mvn -T` (that
is inferior as code wise as capability wise to mvnd) should be simply not used,
maybe even deprecated.
> 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)
