[ http://jira.codehaus.org/browse/MDEPLOY-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183389#action_183389 ]
Guillaume Jeudy commented on MDEPLOY-78: ---------------------------------------- Can anyone tell when 2.5 is due out ? > Deploy with classifier does not deploy pom > ------------------------------------------ > > Key: MDEPLOY-78 > URL: http://jira.codehaus.org/browse/MDEPLOY-78 > Project: Maven 2.x Deploy Plugin > Issue Type: Bug > Affects Versions: 2.3 > Reporter: Libor Kramolis > Assignee: Benjamin Bentmann > 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 is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira