[ 
https://issues.apache.org/jira/browse/MDEPLOY-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14935509#comment-14935509
 ] 

Karl Heinz Marbaise commented on MDEPLOY-176:
---------------------------------------------

The questions is what exactly the issue is with a project with a war file? Can 
create an example project which you put on github or something similar so we 
have something concrete to talk about...

> 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)

Reply via email to