[jbosstools-issues] [JBoss JIRA] (JBIDE-9824) When in zip mode, changing a web project's servlet file inside an ear project does not initiate a proper zipped publish

[Martin Malina (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-9824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12692258#comment-12692258 ] 

Martin Malina commented on JBIDE-9824:
--------------------------------------

Max, I didn't really have any other steps - I was following Rob's steps from description of this JIRA. Now I tried again in JBDS 5.0 Beta3a (H138) and it works as expected. So I am closing this JIRA with fix version Beta3.
                
> When in zip mode, changing a web project's servlet file inside an ear project does not initiate a proper zipped publish
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-9824
>                 URL: https://issues.jboss.org/browse/JBIDE-9824
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS/Servers
>    Affects Versions: 3.3.0.M3
>            Reporter: Rob Stryker
>            Assignee: Martin Malina
>             Fix For: 3.3.0.Beta3
>
>         Attachments: JBIDE-9824.patch
>
>
> Given:
>   1) Create a server, set to not publish automatically, and publish zip style
>   2) An EAR project
>   3) A child WAR project 
>   4) A servlet inside the child .war project
>   5) Add the ear to the server, full publish
>   6) Change the war's servlet
>   7) Perform an incremental publish manually
>   8) Verify zip has been recreated (FAIL)
> Problem seems to stem in the following location:
>   AltMethodZippedJSTPublisher.java, line 93:
>     } else if( publishType != IJBossServerPublisher.NO_PUBLISH ) {
> This line does not take into account that the CHILD modules might have changed, and thus also need updating. 
> This jira will require a unit test. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira