seregamorph commented on issue #12648: URL: https://github.com/apache/maven/issues/12648#issuecomment-5144126101
> This is a deliberate behavioral change in Maven 4, not a bug. The behavior in Maven 3 was a known limitation in its dependency resolution mechanism, which Maven 4 corrects. That's actually the answer the fully satisfies me. For the given dependency it's indeed possible to simply declare the version in the parent pom. Other dependency trees were not affected (at least I do not see it). Thanks for the fast answers @cstamas @elharo 🙏 -- 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]
