You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Karl Heinz Marbaise (Jira)" <ji...@apache.org> on 2019/10/03 15:33:01 UTC

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

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

Karl Heinz Marbaise commented on MNG-6775:
------------------------------------------

Please create an example project and explain exactly what you are trying to achieve...also please add full log files

Furthermore I will move this ticket to the correct location...

> maven-deploy-plugin uses wrong project in deploy-file goal for multi-module project
> -----------------------------------------------------------------------------------
>
>                 Key: MNG-6775
>                 URL: https://issues.apache.org/jira/browse/MNG-6775
>             Project: Maven
>          Issue Type: Bug
>          Components: Deployment
>    Affects Versions: 3.6.2
>            Reporter: Sameer Mene
>            Priority: Major
>
> 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.3.4#803005)