gnodet commented on PR #1148: URL: https://github.com/apache/maven/pull/1148#issuecomment-1592472126
> Maybe we can just drop consumer stuff, since as we proved, model can "move" with existing tech as well? Am just worried about gigantic projects and their heap requirements.. That's really not what the discussions on [dev@](https://lists.apache.org/thread/t0jj2mnwzxyd6oln3r67s78qvw4hdj4n) seem to lead to. The problem does not seem to be maven, but "other"(?) tools which we would not want to break by upgrading the model. So we'll have to forever produce a consumer pom, which means introducing a bom packaging (to differentiate between parent poms and consumed boms). However, I think we should flatten it, so that the used schema is minimal and it will also make things much faster in the long term when all dependencies are flattened. -- 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]
