[
https://issues.apache.org/jira/browse/MDEPLOY-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16943675#comment-16943675
]
Karl Heinz Marbaise edited comment on MDEPLOY-259 at 10/3/19 3:33 PM:
----------------------------------------------------------------------
Please create an example project and explain exactly what you are trying to
achieve...also please add full log files and which JDK versions / plugin
versions etc. you are using...
Furthermore I will move this ticket to the correct location...
was (Author: khmarbaise):
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: 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
>
> 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)
