tree c64a1ba3b2a4b419e3c4554bf28d4de9609210e6
parent 45ae779dc5fcad0140fac01776179882b3cd6b75
author Simon Mavi Stewart <simon.m.stewart@gmail.com> 1768437698 +0000
committer GitHub <noreply@github.com> 1768437698 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsFcBAABCAAQBQJpaDfCCRC1aQ7uu5UhlAAAchwQADoJmsZxRQbEyB8endEJ1NMJ
 LYgjI07NIaf0D19wkqT4Ei5dnrEnqsx/+WyziW4h7MP7WBuDTrMqmgbbkvXa0lel
 doWI5SXMV2JdV0189Td9F/3su5VnCg4dQ22UTOEag5cYHDvjC8RmoIZS2ig4tIun
 1UHyld9xiK5urBaGz8AHQbzL6Z34tT1OicMCYTOKfonbl3HWSLDydVs/9ysIwU5e
 tcIXGln1dO7tQp9Yv7AE1VfosLXa4aAdtQx52Yz4qwR9OLHgS8a0hC6p0ZmBSwVP
 yyzBzjVFzUAfTWPFlCPBfqLj9B4TLaVKV8mZO6lyNHrqkHwJLw4L06SwgaHhGGQa
 V6ZTqpc2qUr96WQ1QFQqkJ3UfhEEz62tXipGEAZIycIsUkFD16e3irdCilbQYhhC
 85SRxYCMDQMbcioQDBX+7FJeE5sZOHjxt+Kas/JyU13AHApKxGIUBKR67ohsSaWh
 UIVBjfCRafLYpsvU2dPd7nEagS/gM4dykhQUQ5vTxpCDuG+x4wI6zQ5G9a4HNdSs
 AgFlyl1oA1j3H7uIVyLl4c2m27VzCBQv5jlNHG/c++XbCSUpW9uSd2gKFTaL7UUJ
 XFrDRq2qOKERKNk24tKeSzQ8be8gLi70yONdcmCWorIU2Y+p4Anx0UcVy7PESqbg
 tPrqrTSqa1UAGPz7jkF1
 =DMYB
 -----END PGP SIGNATURE-----
 

[gradle] Fix Gradle resolver to respect force_version and include runtime dependencies (#1516)

The Gradle resolver was incorrectly retaining aggregating dependencies (dependencies that exist solely to group platform-specific artifacts) in the graph. This occurred because the resolver checked the POM's `packaging` field; if it was `jar` (the default) or missing, the resolver assumed a main JAR artifact must exist, even if Gradle did not resolve one.

This change updates `GradleResolver` to:
1. Remove the logic that infers artifact existence from POM packaging. Instead, it now checks strictly for the presence of non-POM files in the resolved artifacts list.
2. Refine `collapseAggregatingDependencies` to explicitly ignore `javadoc` and `sources` classifiers when determining if a node is an aggregating parent. This ensures standard libraries with documentation or sources attached are not incorrectly identified as aggregating dependencies.

* Avoid creating detached configurations which lead to incorrect versions being fetched

* Use runtime resolution, not just api

* Correctly identify aggregating dependencies by ignoring POM packaging