[MDEPLOY-193] deployAtEnd does not deploy artifacts for multi-module project with build extensions

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.8.2
• Fix Version/s: 3.0.0
• Component/s: deploy:deploy
• Environment: windows 7 / sles 11; maven 3.0.5; java 7u45
• Assignee: Tamas Cservenak
• Reporter: Jörg Sesterhenn
• Created: 01/Dec/14 09:04
• Updated: 20/Oct/22 07:13
• Resolved: 03/Jul/22 18:38

Description

The deploy plugin shows the same behaviour as described in MINSTALL-102.

We noticed that multimodule projects do not deploy any artifacts if there are modules with packagings that add build extensions (e.g. atlassian-plugin, aar = axis archives).

This issue is here for better visibility as discussed in MINSTALL-102.
Please find attached testcase there.

Issue Links

• is related to: MDEPLOY-201 deployAtEnd issue for multi-module projects
• is related to: MDEPLOY-176 With DeployAtEnd activated and a project using customized lifecycle plugin, deploy is skipped
• relates to: MDEPLOY-226 DeployAtEnd fails when module has extension
• relates to: MDEPLOY-157 Add deployAtEnd option for multimodule projects
• links to: GitHub Pull Request #20