[
https://issues.apache.org/jira/browse/MDEPLOY-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965796#comment-17965796
]
Olivier Lamy commented on MDEPLOY-259:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-deploy-plugin#389|https://github.com/apache/maven-deploy-plugin/issues/389].
> 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 (Moved to GitHub Issues)
> 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.20.10#820010)
