Hi Romain, Tamás, Maarten, and Gary, Thanks for sharing this perspective.
I think this highlights an important gap I had not considered earlier. Dependency trees can explain part of the story, but they do not always explain how a dependency actually reaches the final packaged artifact, especially when packaging plugins modify the output. The idea of tracking a dependency from resolution through the build lifecycle into the final artifact is interesting and seems like a valuable direction to explore. I'll look further into what information is already available and what kind of tracking/reporting would be needed. I am also exploring possible GSoC directions around this area, so I would appreciate any feedback from the community on whether this would be a valuable project. If any committer feels this aligns with Maven's needs and would be interested in guiding the work, I would be happy to discuss it further. Thanks again for the insight. Best regards, Hitesh
