gnodet commented on PR #12476: URL: https://github.com/apache/maven/pull/12476#issuecomment-4957408127
Superseded by the resolver-level fix in https://github.com/apache/maven-resolver/pull/1957. After discussion with @cstamas, the root cause was identified as Maven 4 breaking the resolver's single-crossing contract — the `ArtifactDescriptorReader` → `ModelBuilder` → `ModelResolver` chain re-enters `RepositorySystem` during `collectDependencies`, causing `MavenValidator` to reject intermediate state (uninterpolated expressions from transitive POMs). The resolver PR adds re-entrancy detection using `RequestTrace` markers: on the outermost call, a sentinel is stamped into the trace; on re-entry (same thread or pool threads), validation and decoration are skipped. This is a cleaner fix than scattering expression filters across the model builder. Closing in favor of the resolver fix. -- 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]
