ascheman commented on issue #12510: URL: https://github.com/apache/maven/issues/12510#issuecomment-5031001022
@cstamas we re-checked the three "missing exclusions" ITs on 3.10.0-SNAPSHOT — not maven-shade-plugin#819, different mechanism. @slawekjaranowski's #517 already nails it: for `flattenDependencyMode=all`, flatten reads each dependency's exclusions via `readArtifactDescriptor(artifact, null /*repos*/, …)`, which on 3.10 / resolver 2.x can't resolve the MRM-served fixtures without repositories → empty descriptor → no `<exclusion>` written. His one-line `project.getRemoteProjectRepositories()` fixes it — reproduced here: `flatten-dependency-all-transitive` flips from `core` missing its exclusion (assertion fails) to `<exclusion>…:dep</exclusion>` present and green. So plugin-side, #517 covers it; shade#819 stays separate (that one's read-side node pruning). -- 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]
