[
https://issues.apache.org/jira/browse/MDEPLOY-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965599#comment-17965599
]
Olivier Lamy commented on MDEPLOY-78:
-------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-deploy-plugin#436|https://github.com/apache/maven-deploy-plugin/issues/436].
> Deploy with classifier does not deploy pom
> ------------------------------------------
>
> Key: MDEPLOY-78
> URL: https://issues.apache.org/jira/browse/MDEPLOY-78
> Project: Maven Deploy Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 2.3
> Reporter: Libor Kramolis
> Assignee: Benjamin Bentmann
> Priority: Major
> Fix For: 2.5
>
> Attachments: maven-deploy-plugin-2.3.patch
>
>
> This is very similar to MINSTALL-41.
> Problem is that when there is an classifier set to artifact there is no
> primary artifact just pom file. Artifact with classifier is placed in
> attachedArtifacts. It means that it is necessary to deploy POM although there
> is no primary artifact.
> This is fixed by attached patch. There is a new method deploy i a class
> DeployMojo. This class is subset of same named method of Maven core
> DefaultArtifactDeployer class. It would be better to change core
> DefaultArtifactDeployer to ignore null File source argument.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
