[ https://issues.apache.org/jira/browse/MNG-7501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17690638#comment-17690638 ]
Michael Osipov commented on MNG-7501: ------------------------------------- Fixed with [47bf22022d79a611cdbecc49cc2fa51d84306835|https://gitbox.apache.org/repos/asf?p=maven.git&a=commit&h=64da2c58243bc6f48827301b744b9f6312497550] for {{maven-3.8.x}} branch. > 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-2, 4.0.0, 3.8.8 > > > 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.10#820010)