[jira] [Commented] (MDEPLOY-259) maven-deploy-plugin uses wrong project in deploy-file goal for multi-module project

["Tamás Cservenák (Jira)" <ji...@apache.org>]

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

Tamás Cservenák commented on MDEPLOY-259:
-----------------------------------------

Most probably gone after MDEPLOY-296

> maven-deploy-plugin uses wrong project in deploy-file goal for multi-module project
> -----------------------------------------------------------------------------------
>
>                 Key: MDEPLOY-259
>                 URL: https://issues.apache.org/jira/browse/MDEPLOY-259
>             Project: Maven Deploy Plugin
>          Issue Type: Bug
>    Affects Versions: 3.0.0-M1
>            Reporter: Sameer Mene
>            Priority: Major
>             Fix For: waiting-for-feedback
>
>
> Multi-Module project
> A
> | - B
> |   |  - B1
> |   |  - B2
> | - C
>  
> There is a deploy-file goal in project B1 and C using maven-deploy-plugin. B1 is able to upload the file properly but while uploading C's file it uses the artifact name of B2 or B1 (random)
>  
> In DeployFileMojo.java
> {code:java}
>  DefaultProjectBuildingRequest buildingRequest =
>             new DefaultProjectBuildingRequest( getSession().getProjectBuildingRequest() );{code}
>  
> returns the wrong ProjectBuildingRequest and so it take a differnt project name.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)