[jbosstools-issues] [JBoss JIRA] (JBIDE-24522) Incremental deployment for WF11/EAP7.1 - only redeploy if necessary

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-24522:
-------------------------------------

So I made a patch to fix this. It... works... a bit better than before.   Changes to only an index.html will not initiate a redeployment. However, if the server is in debug mode, and you try to change a class file, and you have a breakpoint set there, it won't work properly, at all. 

I'll be pinging the EAP team to help me debug it asap. For now, a proper workaround is to change the "Application Reload Behavior" field in the server editor to something like "\.jar$|\.class$" AND disable the breakpoint, then refresh the webpage, then enable the breakpoint to debug it. 

This will force a redeploy to occur if any class files have changed. Why the normal remote debugger isn't working is very difficult to tell. 

Either way, this definitely improves the situation. It may make sense to change the default pattern to be "\.jar$|\.class$" all the time. But I'm hesitatn to do that until I know what effect it would have on other situations. 

> Incremental deployment for WF11/EAP7.1 - only redeploy if necessary
> -------------------------------------------------------------------
>
>                 Key: JBIDE-24522
>                 URL: https://issues.jboss.org/browse/JBIDE-24522
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: server
>    Affects Versions: 4.5.0.AM1
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>             Fix For: 4.5.0.AM1
>
>
> As discussed with Rob, JBIDE-23784 added support for incremental deployment over management API for WildFly 11 / EAP 7.1. But it does not actually deploy incrementally. It will still redeploy the whole module on the server. The improvement that was done in that JIRA is that now the whole project is not copied over to the server every time there is a change - now only the changes are being sent. But the whole module is still redeployed.
> So I think it's worth looking into if it's possible to improve this further so that the module is not always redeployed on the server.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)