hboutemy commented on PR #1211: URL: https://github.com/apache/maven/pull/1211#issuecomment-1656677402
first, https://issues.apache.org/jira/projects/MPH/issues/MPH-183 should be solved, because currently there is absolutely nothing to debug dependencyManagement imports, and the sigstore-maven-plugin case showed that when you have such imports chained everywhere, it's really hard to understand how the dependencyManagement went in food for thought: Maven core logging does not log anything at all about reactor dependencies effective POM building nor dependencies resolution. That's why we rely (and we should make it clear to end-users) on `mvn help:effective-pom -Dverbose` for effective POM debugging and `mvn dependency:list` / `mvn dependency:tree -Dverbose` for dependency resolution debugging should we add log to Maven core for effective POM building? I'm not convinced, because it will become too chatty I fear should we add WARN on dependencyManagement import precedence decision: I'm definitively against it, because that's not a WARN: that would be at most an INFO perhaps we need a better documentation, because I'm convinced many details are misunderstood -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
