[
https://issues.apache.org/jira/browse/MPH-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17878092#comment-17878092
]
Jeremie Bresson commented on MPH-175:
-------------------------------------
I think the feature you are interested in is provided by the
flatten-maven-plugin
https://www.mojohaus.org/flatten-maven-plugin/index.html
{code:xml}
<dependency>
<groupId>org.codehaus.mojo</groupId>
<artifactId>flatten-maven-plugin</artifactId>
<version>${version}</version>
</dependency>
{code}
> mvn help:effective-pom leaves <parent> pom in place
> ---------------------------------------------------
>
> Key: MPH-175
> URL: https://issues.apache.org/jira/browse/MPH-175
> Project: Maven Help Plugin
> Issue Type: Bug
> Components: effective-pom
> Affects Versions: 3.2.0
> Environment: MacOS
> Reporter: Georg Lippold
> Priority: Minor
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> When executing mvn help:effective-pom, the <parent> XML node is left intact.
> The <parent> should be removed in the effective POM.
> If you generate the effective pom to modify the project, e.g. to remove or
> override settings that are present in the parent pom, then including the
> <parent> node in the resulting XML re-introduces the settings that you wanted
> to modify.
> Example: <parent> specifies a setting, e.g.
> {code:xml}
> <project>
> <properties>
> <format>HTML</format>
> </properties>
> </project>
> {code}
> If the <format> node is now removed from the effective POM, then it is
> re-introduced by including the <parent> in every maven run. The parent POM
> should not be required anymore in an effective POM, because all its settings
> should already be included in the effective POM.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)