cstamas commented on PR #2147: URL: https://github.com/apache/maven/pull/2147#issuecomment-2704174587
> Why do we consider a conflict if the extension is the same (same GAV + same config) ? That's not really a conflict. A conflict would be a different version or different config imho. We consider it as "conflict" for simplicity sake: I'd not go down the route to have "model builder" for extensions, and "build" the model out of 3 sources. Even if same GAV of extension, project one may have different config due some requirement while user wide another config, etc. I handle them _dead simple_: they are considered as "blob" (atom?) keyed by GA and no merging or building or whatsoever magic happens, basically rules are simple: * one XML file must be GA unique (having two different entries Vs for same GA is most probably error; nor Maven can handle that) * across 3 possible sources precedence wins -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
