jjj-n commented on issue #1051: URL: https://github.com/apache/maven-resolver/issues/1051#issuecomment-5487598948
Hi @slachiewicz, I'd like to take this issue and investigate a code fix. I understand that the remaining open question is whether the range/relocation interaction should be fixed or documented as an edge case. Before changing behavior, I plan to add a focused regression fixture on current main that reproduces the case for both the depth-first and breadth-first collectors, then trace where relocation and version-range resolution diverge. Could you confirm the intended result for the verbose dirty tree? My current understanding is: - the normal resolved dependency tree should contain only the selected winner, C3; - the verbose dirty tree should retain C1, C2, and C3, with only their ordering allowed to differ between the DF and BF collectors. If that is the expected contract, I will proceed test-first, make both collectors follow the same semantics, and add regression coverage for the range-plus-relocation case. -- 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]
