[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-9112) AS7: deployment fails when switching from zipped -> exploded deployment and changing a single resource

[Rob Stryker (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-9112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Stryker resolved JBIDE-9112.
--------------------------------

    Resolution: Done


When the publisher fails to make the correct copy, the module publish state is set to full-publish needed, since it is unsure of exactly what file failed, and caching all that would be a ton of work and make future deltas useless. So, after one failure, you get the error dialog, but the next publish attempt is a full publish. This is the current behaviour. 

Since previously users were deploying zipped (thus long deployments, not small incremental ones), and now they switched to exploded, it is completely reasonable (and expected) that the first incremental publish in that situation be a full publish. For this reason, I've added some API and now the first publish after such a property change will force a full publish. 

> AS7: deployment fails when switching from zipped -> exploded deployment and changing a single resource
> ------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-9112
>                 URL: https://issues.jboss.org/browse/JBIDE-9112
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 3.3.0.M1
>         Environment: JBoss AS7 Beta4
>            Reporter: Andre Dietisheim
>            Assignee: Rob Stryker
>             Fix For: 3.3.0.M3
>
>         Attachments: deployment-error.png
>
>


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira