[MDEPLOY-176] With DeployAtEnd activated and a project using customized lifecycle plugin, deploy is skipped

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 2.8.1, 2.8.2
• Component/s: deploy:deploy
• Environment: Maven 3.0.5
• Assignee: Robert Scholte
• Reporter: olivier o
• Created: 24/Mar/14 12:32
• Updated: 04/Nov/16 12:53
• Resolved: 30/Sep/15 14:46

Description

Hi,
When deployAtEnd is enabled, the deployment of all modules is skipped. It seems that the "readyProjectsCounter" is not accurate for one module. So the last module is not detected.

I've attached a simple sample project with 4 modules :

• pom : set version and plugin management
• jar and ear : empty project (only to illustrate counter reset)
• war : module with readyProjectsCounter

I've looked at 2.9-SNAP version code , and displayed some info from attached sample :
pom : readyProjectsCounter: 1 - reactorProjects: 4
jar: readyProjectsCounter: 2 - reactorProjects: 4
war: readyProjectsCounter: 1 - reactorProjects: 4
ear: readyProjectsCounter: 3 - reactorProjects: 4

Regards,
Olivier

Issue Links

• is related to: MDEPLOY-201 deployAtEnd issue for multi-module projects
• relates to: MDEPLOY-157 Add deployAtEnd option for multimodule projects
• relates to: MDEPLOY-193 deployAtEnd does not deploy artifacts for multi-module project with build extensions