gnodet commented on PR #1437: URL: https://github.com/apache/maven/pull/1437#issuecomment-6191180179
Thanks for the contribution @laeubi. The discussion here highlighted the core issue: adding `set/getConsumerPom()` to `MavenProject` (the legacy v3 class) isn't the right approach, as that class is being phased out in Maven 4. The correct solution is to model this in the Maven 4 API — likely via `org.apache.maven.api.Project` or the relevant Session/lifecycle layer — where the build-vs-consumer POM distinction can be handled cleanly and without the file-mutation side effects that plague the current approach. Closing in favor of a proper Maven 4 API design. The JIRA issue MNG-8072 should be kept open to track that work. -- 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]
