[
https://issues.apache.org/jira/browse/MDEPLOY-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17924926#comment-17924926
]
Matthias Bünger commented on MDEPLOY-326:
-----------------------------------------
{quote}
I think that is it issue for Maven ... deploy plugin simply transfer all
attached artifacts.
So Maven should not attach this one to project.
{quote}
So I bet on the wrong 50% when I was asking myself if it is a Maven or a Maven
Deploy-plugin :/
Created an issue in Maven JIRA as I can't move this one.
[~sjaranowski] Please close this one - thanks. (I wait for merging this JIRA
account with my ASF one and Infra said I should not use the ASF one to make it
easier).
> Maven 4: Don't deploy build POM
> -------------------------------
>
> Key: MDEPLOY-326
> URL: https://issues.apache.org/jira/browse/MDEPLOY-326
> Project: Maven Deploy Plugin
> Issue Type: Improvement
> Affects Versions: 3.1.3
> Reporter: Matthias Bünger
> Priority: Major
>
> Topic came up on ML (by Lars Bruun-Hansen)
> As of now the Maven 4 build POMis 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)
