maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bentmann (JIRA)" <j...@codehaus.org>
Subject [jira] Closed: (MDEPLOY-78) Deploy with classifier does not deploy pom
Date Sun, 15 Mar 2009 21:44:13 GMT

     [ http://jira.codehaus.org/browse/MDEPLOY-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Benjamin Bentmann closed MDEPLOY-78.
------------------------------------

         Assignee: Benjamin Bentmann
       Resolution: Fixed
    Fix Version/s: 2.5

Fixed in [r754768|http://svn.eu.apache.org/viewvc?view=rev&revision=754768].

> 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

        

Mime
View raw message