[
https://issues.apache.org/jira/browse/MNG-7501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed MNG-7501.
------------------------------
Assignee: Herve Boutemy
Resolution: Fixed
done:
- in
https://github.com/apache/maven/commit/c9a3e0e45b0a6e7eca29d150443b04c9c99f3813
for Maven 3.9.x
- in
https://github.com/apache/maven/commit/4e88d62ab23a2cef8b1ec8af479353bc4d86fe25
for master / Maven 4
> 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
> Assignee: Herve Boutemy
> Priority: Major
> Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> 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)
