rmannibucau commented on PR #11904: URL: https://github.com/apache/maven/pull/11904#issuecomment-6294886201
A few note - don't take them all as a "no" but more as what was my expectations on this topic: * groupId:artifactId:type:classifier:version * no need of trailing ":" hack, a managed version has no version tag so not an issue * i wouldnt collapse scope at all, it is harder to read, misleading and not the identity of the dependency at all * why would exclusions not be inlined? * never infer groupId, can only lead to issues * must include extensions, plugins, etc... too more generally speaking not collapsing anything but keeping 1 value per "field" sounds saner on the long run (ivy style) cause it doesn't imply to create a custom language in another language (xml) which is saner and more tool friendly (i know xslt 3 enables crazy things but let's not need it). Will also solve the `groupId:artifactId:type:classifier:version` order definition which is very misleading, not normalized and generally enforces to type more info than needed. So overall I would just move children as attributes and drop the inference for groupId. That's the best outcome I went with this topic over the last years of discussion. -- 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]
