Hello again, I tried to create a proposal in/under https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=5964567, but I'm not allowed to, which makes sense since I'm new to the wiki, so I committed a proposal to my fork: https://github.com/strohmattenverleger/maven/blob/MNG-4530/Dependency-Overrides.md
The current version probably still contains errors and misses details but I imo they need to be worked out in a group effort. Some feedback/comments would be appreciated. Maybe you could create a proposal page in your wiki and grant me edit rights (user eth)? Kind regards Enno ________________________________ From: Enno Thieleke <enno.thiel...@holisticon.de> Sent: Thursday, August 26, 2021 11:59 AM To: Maven Developers List <dev@maven.apache.org> Subject: Re: Request for Enhancement: Dependency Overrides Hi Michael, I'll take this as a "go ahead, if it's good we'll accept it". Just a few more questions before I start. For the issue: Would reopening https://issues.apache.org/jira/browse/MNG-4530 suffice or would you like to see a new one? Where do I create the proposal? What should be created first, the issue or the proposal? I'm asking, because in the proposal we'd work out the details and after that's done, that's where the issue becomes relevant (no issue, no code changes). At least that's how I'm used to implementing changes like this. I don't want to have created unnecessary noise in your issue system, if - for some unknown eventuality - the proposal doesn't get your approval. Is it ok to use one issue for changes in both projects, Maven and maven-resolver? Kind regards Enno ________________________________ From: Michael Osipov <micha...@apache.org> Sent: Wednesday, August 25, 2021 9:01 PM To: dev@maven.apache.org <dev@maven.apache.org> Subject: Re: Request for Enhancement: Dependency Overrides Am 2021-08-25 um 20:51 schrieb Enno Thieleke: > Hello again, > > some days have passed and I didn't want to distract you people from releasing > the new version of Maven, but now that it's done, I'm getting back to this > topic. > > I'm asking for the opinion of the Maven PMC and committers regarding this > feature. I'd like to see some sort of dependency override/replacement > mechanism. One that's powerful, yet easy to use, which doesn't require > boilerplate XML and which leaves the dependency graph virtually untouched (by > that I mean the shape of the graph remains the same, unless additional > transitive dependencies are brought into play by overrides/replacements). > > Please let me know what you people think of such a feature. Maybe a vote is > in order, but I'm not sure and I wouldn't know how to call for one properly > here. Please tell me how to proceed. I'm only willing to commit more time to > this, if I have an ok from you that it'll be merged once it meets the quality > standards of the Maven project. As I said previously, this perfectly makes sense, but having this in Core means that someone needs to create an issue, proposal and a PR. Consider that no one of us is getting paid on this, so free time only. Unless it comes from the community, I see little chances to have this soon. Michael --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
