[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-6024) JBoss AS adapter deploys only recently changed files and removes everithing else

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen updated JBIDE-6024:
---------------------------------------

    Fix Version/s: 3.1.1
                       (was: 3.1.0.GA)


To All: After discussing this and trying to reproduce more consistently (and failing to do so) and that it seems to only happen for some EAR deployments and is workaroundable with a full publish we acknowledge that the bug exists and should be fixed ASAP, but that we don't expect to hold back GA for this. 

To Rob: looking at JstPublisher.fullPublish it seems like EAR fullpublish triggers a full delete which deletes everything in it (including just published War and Ear's) causing that only the subsequent incremental publish to actually be visible. This is just based on reading the code since I haven't been able to reproduce a situation where Ear gets deployed last.




> JBoss AS adapter deploys only recently changed files and removes everithing else 
> ---------------------------------------------------------------------------------
>
>                 Key: JBIDE-6024
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-6024
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 3.1.0.CR2
>         Environment: JBoss Tools 3.1.0.GA candidate v201003050540R-H56-GA
>            Reporter: Denis Golovin
>            Assignee: Rob Stryker
>            Priority: Blocker
>             Fix For: 3.1.1
>
>
> The steps to replicate the issue are explained in this post http://community.jboss.org/message/526847#526847. 
> I cannot confirm yet but it looks like problem should be replicated for any project after couple hours of waiting.
> I was able to get the same problems after I tried to change ad deploy files after 4 hours. Now it happens every time even after restoring deployment with Full Publish action in Servers View

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira