[
https://issues.apache.org/jira/browse/MNG-5586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliotte Rusty Harold resolved MNG-5586.
----------------------------------------
Resolution: Duplicate
This seems likely to be delivered under the build/consumer POM work in maven 4
> Deploy effective pom
> --------------------
>
> Key: MNG-5586
> URL: https://issues.apache.org/jira/browse/MNG-5586
> Project: Maven
> Issue Type: Improvement
> Components: Deployment
> Reporter: nicolas de loof
> Priority: Major
>
> When deploying pom for an artifact, maven deploys the actual file used to
> build. As this one can define profiles, and build can rely on command line
> properties that change actual project model, the deployed pom.xml may not
> reflect the one used by maven to build the project. Also, this prevent
> changes to happen in pom.xml format (wildcard exclusion for sample) without
> breaking compatibility.
> Maven should deploy effective pom when artifact doesn't define pom packaging
--
This message was sent by Atlassian Jira
(v8.20.10#820010)