You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Slawomir Jaranowski (Jira)" <ji...@apache.org> on 2025/02/07 07:25:00 UTC

[jira] [Commented] (MDEPLOY-326) Maven 4: Don't deploy build POM

    [ https://issues.apache.org/jira/browse/MDEPLOY-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17924789#comment-17924789 ] 

Slawomir Jaranowski commented on MDEPLOY-326:
---------------------------------------------

I think that is it issue for Maven ... deploy plugin simply transfer all attached artifacts.

So Maven should not attach this one to project.

> 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)