[ https://issues.apache.org/jira/browse/MDEPLOY-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14936788#comment-14936788 ]
Karl Heinz Marbaise commented on MDEPLOY-176: --------------------------------------------- You wrote your deploy is working with Maven 2.2.1 Ok..first Maven 2.2.1 does not support parallel builds and of course do you use parallel builds like {{mvn -T 4 clean deploy}} ?...Furthermore does your build work with an empty local cache which means a simple {{mvn clean package}} will it work ? Apart from that what version of {{maven-war-plugin}} do you use? And as a asked before can you make an example project which shows the wrong behaviour ? > 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 > Issue Type: Bug > Components: deploy:deploy > Affects Versions: 2.8.1, 2.8.2 > Environment: Maven 3.0.5 > Reporter: olivier o > Attachments: deploy-end-fail.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 (v6.3.4#6332)