[jbosstools-issues] [JBoss JIRA] (JBIDE-21481) [server adapter] Allow publishing of wtp-style projects

[ https://issues.jboss.org/browse/JBIDE-21481?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21481: ------------------------------------- To properly get WTP-style projects deployed, a significant number of changes really need to be made to openshift server adapter. In reality, the behavior of the server should really be customized based on what we know of the pod's type (if it's possible to get such information). If we know the POD is an eap server, we'd use a lot of logic from astools, including being able to set .dodeploy markers and check server status and module deployment status. If the remote pod is something set up for node.js or php or other simple file-tree style projects, it'd use a much more simplified set of logic without any of these extras built in. The currently attached PR doesn't do the .dodeploy stuff, and so in reality, this patch only really allows changes to html files unless the user is willing to go in and touch the .dodeploy file in the (workspaceroot)/.metadata/.plugins/org.jboss.ide.eclipse.as.core/eap-app_at_OpenShift_3_(192.168.121.62)/deploy/ROOT.war.dodeploy file. However, once the user does that once, all future rsync's seem to always initiate a new full reload of the app on the server, and so we stop getting class errors when executing actions on kitchensink that require interaction with servlets or classes. Obviously this behaviour isn't ideal, since setting the .dodeploy once will result in every publish being a full restart of the module. But I think this patch is valuable for a beta2 to get some more user feedback on how it's working, what doesn't flow, and what can be improved. -- This message was sent by Atlassian JIRA (v6.4.11#64026)