[MDEPLOY-226] DeployAtEnd fails when module has extension

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.8.2
• Fix Version/s: 3.1.0
• Component/s: deploy:deploy
• Assignee: Slawomir Jaranowski
• Reporter: Charles Honton
• Created: 19/Nov/17 18:58
• Updated: 31/Jan/23 15:44
• Resolved: 28/Jan/23 18:18

Description

Setup:
Aggregator pom has deployAtEnd=true
Any module has additional extension

Expected:
All modules and aggregator batched to single deploy at end

Actual:
No modules nor aggregator are deployed

Issue Links

• is duplicated by: MDEPLOY-234 Nothing is deployed if deployAtEnd=true and extension is added in submodule
• is fixed by: MDEPLOY-305 Improvement in DeployAtEnd
• is fixed by: MDEPLOY-296 Cleanup the plugin
• is related to: MDEPLOY-193 deployAtEnd does not deploy artifacts for multi-module project with build extensions
• is related to: MDEPLOY-200 deployAtEnd fails if the last project to build skip deployment
• is related to: MDEPLOY-224 Overriding deployAtEnd fails
• is related to: MDEPLOY-225 DeployAtEnd fails when overriding skip
• is related to: MDEPLOY-102 Allow deploy:deploy-file to specify the extension of the artifact
• links to: GitHub Pull Request #138