gnodet commented on PR #13256: URL: https://github.com/apache/maven/pull/13256#issuecomment-5808653325
Addressed the test validity issue: The test now calls `getPath(pomArtifact)` **before** `setPath()` to confirm the bug condition — the JAR path set by `jar:jar` is returned from the project-artifact loop (when the `paths` map is still empty). Then after `setPath()`, it verifies the POM path is returned, confirming the priority fix works. A comment also documents the `setPath()` side-effect (it calls `setFile()` on the legacy artifact), explaining why both old and new code return the correct path post-`setPath()` — but only the fixed code gets it right in the pre-`setPath()` window that actually matters. -- 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]
