hboutemy commented on issue #11772: URL: https://github.com/apache/maven/issues/11772#issuecomment-4029112581
@gnodet I'm looking at this > But since child artifact consumer POMs retain a <parent> reference from the thinking we had in the past about build/consumer POMs, at that time we thought about the question of parent POMs published to Maven Central. At that time, because of the complexity of profiles etc..., we thought that for parent POMs, it was very "build-only" then: 1. parent would be published only in their original form, 4.1.0 when project upgrades 2. child artifacts would drop their parent link in the consumer POM and just become standalone without parent, to avoid the new format at that time, this was thought as the most simple is there a reason to not "just" do that, beyond the impact on size of the child consumer POM = the key impact we found? Is there a strong win at keeping a parent to a consumer POM? -- 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]
