elharo commented on issue #306: URL: https://github.com/apache/maven-help-plugin/issues/306#issuecomment-5117544768
Per Gemini: This is not a bug, and it is an unreasonable request based on a misunderstanding of the `maven-help-plugin`'s purpose. The user is attempting to use a diagnostic tool as an export tool, which is an anti-pattern in Maven. The request is flawed for the following technical reasons: 1. **Diagnostic vs. Transformation Purpose:** The `help:effective-pom` goal is strictly a diagnostic tool designed to display the POM that Maven uses during a build, after inheritance, interpolation, and active profiles are resolved. It is meant to be read by developers to troubleshoot builds, not to be saved and used as a replacement `pom.xml`. 2. **Model Integrity:** In the Maven Project Object Model (POM), inheritance is a core structural element. Even after properties and plugin configurations are interpolated from the parent, the project's identity (and often its implicit `groupId` and `version`) remains tied to that parent. Removing the `<parent>` node would inaccurately represent the Maven project state. 3. **Existing Tooling:** The specific use case the user describes—generating a resolved, standalone POM that strips out the parent hierarchy so it can be deployed or modified independently—is exactly what the `flatten-maven-plugin` is designed to do. While the issue was imported from Jira with a `bug` label, the described behavior is the correct and intended functionality of `mvn help:effective-pom`. Modifying it to drop the `<parent>` tag would break its diagnostic accuracy. I'm not actually 100% convinced of this, so if someone wants to argue otherwise, please comment and we can consider reopening. -- 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]
