[
https://issues.apache.org/jira/browse/MDEPLOY-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965722#comment-17965722
]
Olivier Lamy commented on MDEPLOY-176:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-deploy-plugin#354|https://github.com/apache/maven-deploy-plugin/issues/354].
> With DeployAtEnd activated and a project using customized lifecycle plugin,
> deploy is skipped
> ----------------------------------------------------------------------------------------------
>
> Key: MDEPLOY-176
> URL: https://issues.apache.org/jira/browse/MDEPLOY-176
> Project: Maven Deploy Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Components: deploy:deploy
> Affects Versions: 2.8.1, 2.8.2
> Environment: Maven 3.0.5
> Reporter: olivier o
> Assignee: Robert Scholte
> Priority: Major
> Attachments: deploy-end-fail.zip, deployAtEndFailure.zip
>
>
> 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
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
