gnodet commented on PR #2009: URL: https://github.com/apache/maven-resolver/pull/2009#issuecomment-5058397913
Thanks for the feedback @cstamas! You're right — removing managed dependency validation entirely is too broad. I've reverted the managed dependency validation changes in 74005921. This PR now focuses solely on **session-scoped re-entrancy detection** (the `AtomicInteger` depth counter in session data), which addresses the broken trace chain scenario independently of the managed dependency question. The managed dependency separation (direct vs managed validation) is better handled by #2008's `validateManagedDependency()` approach, which lets MavenValidator abstain while keeping the validation available for non-Maven consumers. -- 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]
