arturobernalg opened a new pull request, #1814:
URL: https://github.com/apache/maven-dependency-plugin/pull/1814

   #1813: the get-classpath IT's `verify.groovy` hard-coded the classpath order 
as `[lib, dep, runtime, leaf]`, but that's only correct on Maven 3.10+/4 
(Resolver 2.x). On Maven 3.9 and earlier (Resolver 1.x), a transitive 
dependency reached only through another dependency (the leaf, reached via dep) 
sorts before that dependency's own siblings (runtime), so the actual order is 
`[lib, dep, leaf, runtime]`. The goal itself is correct; the IT's expectation 
wasn't. CI only runs Maven 3.10/4, so this never showed up there, but it fails 
on Maven 3.9.16 which the plugin's own `<prerequisites>` still allows.
   
   Build the expected order per Maven version, the same way the IT already does 
for the leaf's own version. Reproduced the exact failure from the issue on real 
Maven 3.9.16 before the fix, confirmed it passes after.
   
   ---
   
   To make clear that you license your contribution under
   the [Apache License Version 2.0, January 
2004](https://www.apache.org/licenses/LICENSE-2.0)
   check one of the following:
   
   - [x] I hereby declare this contribution to be licensed under the [Apache 
License Version 2.0, January 2004](https://www.apache.org/licenses/LICENSE-2.0)
   - [ ] I hereby declare that I have filed an [Apache Individual Contributor 
License Agreement](https://www.apache.org/licenses/icla.pdf).
   
   https://claude.ai/code/session_01BrsHTdDq7PD1DoqeA9vs66


-- 
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]

Reply via email to