gnodet commented on PR #1599: URL: https://github.com/apache/maven-dependency-plugin/pull/1599#issuecomment-4180646434
> Hey @gnodet, you requested changes here, but then you also created a competing PR #1600. > > I'm cool with that, because all I want is to be able to do `mvn dependency:add`. Having the credit to an open source contribution is far from my priorities. Yes, I tasked an AI agent to see what it would give with the changes I wanted, and got caught in the process... and I really don't care about the credit either... A major point, which I think is really important, is the ability to actually use those new goals on real projects, not just starter projects with a very simple structure. So we need to support adding agents and kinda follow the existing organisation/layout of the project. Which means, not only simply adding a dependency, but adding it the way other dependencies are expressed: this includes adding a managed dependency in a top level parent and/or using a property. That's already implemented in my alternative PR. > So for this reason, I will focus on @rmannibucau's feedback for now, as I see this approach straightforward and not dependant on non-Apache libraries like `domtrip`. Given 99% of the code has been written by Maven committers, directly for Maven or related projects, and given the fact it's already a dependency of Maven 4, I don't really think that's a problem. -- 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]
