cstamas commented on PR #1633: URL: https://github.com/apache/maven/pull/1633#issuecomment-2280379191
@WolfgangHG I think always printing out path would be "too much", Maven is already way way too chatty... but here are few facts to tinker about: * when descriptor reader reports this error all Maven "knows" that some POM somewhere has some issue (uses system scoped dependency pointing at file that does not exists) * later on, when collection happened (built the "dirty graph" -> conflicts resolved -> dep tree), just as in this example, the reported POM may not even be present... * still, IMO developer _should be aware_ of issues like these, as any dependency change/reshuffle may make the offending POM end up in the build (in reproducer is "just lurking somewhere" but is not entering -- is eliminated) So IMO one liner is fine, and will add "use -X for full details" -- 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
