[
https://issues.apache.org/jira/browse/MNG-8568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17925942#comment-17925942
]
Guillaume Nodet commented on MNG-8568:
--------------------------------------
I'm not sure we want to switch it off. It should at least be configurable, and
I'm leaning towards keeping the deployed build pom the default behavior.
> Maven 4: Don't deploy build POM
> -------------------------------
>
> Key: MNG-8568
> URL: https://issues.apache.org/jira/browse/MNG-8568
> Project: Maven
> Issue Type: Improvement
> Components: Deployment
> Affects Versions: 4.0.0-rc-2
> Reporter: Matthias Bünger
> Priority: Major
>
> Topic came up on ML (by Lars Bruun-Hansen)
> As of now the Maven 4 build POM is deployed together with the consumer POM,
> but is of no use for the consumer. Even more it might contain "internal"
> information.
> So the idea is to not deploy the build POM, but only the consumer POM.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
