arturobernalg commented on issue #11266: URL: https://github.com/apache/maven/issues/11266#issuecomment-6215096491
I could reproduce this, and it fails the same way on Maven 3.9.16 and on current master (4.1.0-SNAPSHOT), so it does not look like a regression. Reproducer: a repository with `g:dep:1` (a jar plus a POM) whose POM declares the parent `g:missing-parent:9`, which is not published anywhere. A project that depends on `g:dep:1` fails with `mvn dependency:resolve`: ``` Failed to execute goal on project p: Could not collect dependencies for project t:p:jar:1 Failed to read artifact descriptor for g:dep:jar:1 Caused by: The following artifacts could not be resolved: g:missing-parent:pom:9 (absent): Could not find artifact g:missing-parent:pom:9 in myrepo ``` As far as I can tell, Maven only tolerates a missing POM of the dependency itself with a warning, not a POM whose parent cannot be resolved, which it treats as an invalid descriptor. I did not test older versions, so I cannot say whether it ever behaved differently. @laeubi, which Maven version did you see the warning with? Making this lenient would be a behavior change, so I would like a maintainer's opinion before sending any change. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
