[jbosstools-issues] [JBoss JIRA] (JBIDE-26694) Server adapter: should be able to freely set a war name

[ https://issues.jboss.org/browse/JBIDE-26694?page=com.atlassian.jira.plugi... ] André Dietisheim updated JBIDE-26694: ------------------------------------- Description: For the server adapters in tools/as we have UI that allows a user to set the name of the deployment archive. We're missing this feature for the OpenShift server adapters currently. We're asked to add it. Steps: # EXEC: create a new app by using the *jboss-webserver31-tomcat8-openshift:1.2* builder image # ASSERT: *websocket-chat* application is imported into your workspace # ASSERT: server adapter *jboss-webserver31-tomcat* is created # ASSERT: In OpenShift explorer, below the service jboss-webserver31-tomcat*, you have the running pod (build is finished, pod running) # EXEC: start the server adapter # ASSERT: RSync is executed and the output is visible in the "Console" Result: If you look closely at the output you see that the project is synced to the pod in a folder called *websocket-chat.jar* !console-output-1.png! Expected result: I should be able to set the output folder to anything I want. Ex. we have a customer that wants the application war to be synced up into a folder *ROOT* (without the extension *.war*). Currently, to achieve this I have to do the following: # EXEC: open the properties for the server adapter and hit "Switch Location" !switch-location.png! # ASSERT: in my workspace, a new project *Servers* is created. It contains the configuration for my server adapter. !server-adapter-configuration.png! # EXEC: open the file with the *XML Editor* # EXEC: create the following xml snippet (notice the *outputName* property for the module) and make sure it reads as follows: {code} <?xml version="1.0" encoding="UTF-8"?> <deployment> <local> <module id="org.eclipse.jst.jee.server:websocket-chat"> <property key="tempLocation" value="" /> <property key="location" value="" /> <property key="outputName" value="ROOT" /> </module> </local> </deployment> {code} # EXEC: html-encode and join it into a single line # EXEC: in your *XML* editor for the server adapter: go to the end of the line *<server auto-publish-setting="2"* and insert your html-encoded xml as a value to the attribute *org.jboss.ide.eclipse.as.core.util.deploymentPreferenceKey="* {code} <?xml version="1.0" encoding="UTF-8" standalone="no"?> <server auto-publish-setting="2" auto-publish-time="2" hostname="jboss-webserver31-tomcat-test.192.168.64.76.nip.io" id="test@jboss-webserver31-tomcat" id-set="true" name="jboss-webserver31-tomcat (Service) at OpenShift 3 (192.168.64.76)" org.jboss.ide.eclipse.as.core.server.IGNORE_LAUNCH_COMMANDS="true" org.jboss.ide.eclipse.as.core.server.deployDirectoryType="custom" org.jboss.ide.eclipse.as.core.server.serverMode="openshift3" org.jboss.ide.eclipse.as.core.server.webPort="80" org.jboss.ide.eclipse.as.core.server.webPortAutoDetect="false" org.jboss.ide.eclipse.as.core.server.zipDeploymentsPreference="true" org.jboss.tools.openshift.Connection="https://developer@192.168.64.76:8443" org.jboss.tools.openshift.DeployProject="websocket-chat" org.jboss.tools.openshift.PodPath="/opt/webserver/webapps" org.jboss.tools.openshift.SERVER_START_ON_CREATION="false" org.jboss.tools.openshift.Service="test@jboss-webserver31-tomcat" org.jboss.tools.openshift.SourcePath="${workspace_loc:/websocket-chat}" port="80" runtime-id="test@jboss-webserver31-tomcat" server-type="org.jboss.tools.openshift.server.type" server-type-id="org.jboss.tools.openshift.server.type" start-timeout="450" stop-timeout="450" timestamp="2" org.jboss.ide.eclipse.as.core.util.deploymentPreferenceKey="&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt; &lt;deployment&gt; &lt;local&gt; &lt;module id=&quot;org.eclipse.jst.jee.server:websocket-chat&quot;&gt; &lt;property key=&quot;tempLocation&quot; value=&quot;&quot; /&gt; &lt;property key=&quot;location&quot; value=&quot;&quot; /&gt; &lt;property key=&quot;outputName&quot; value=&quot;ROOT&quot; /&gt; &lt;/module&gt; &lt;/local&gt; &lt;/deployment&gt;"> <list key="modules" value0="websocket-chat::org.eclipse.jst.jee.server:websocket-chat::jst.web::3.0"/> </server> {code} # EXEC: Save the editor and restart the server Result: Syncing now happens into a folder *ROOT* !console-output-2.png! was: For the server adapters in tools/as we have UI that allows a user to set the name of the deployment archive. We're missing this feature for the OpenShift server adapters currently. We're asked to add it. Steps: # EXEC: create a new app by using the *jboss-webserver31-tomcat8-openshift:1.2* builder image # ASSERT: *websocket-chat* application is imported into your workspace # ASSERT: server adapter *jboss-webserver31-tomcat* is created # ASSERT: In OpenShift explorer, below the service jboss-webserver31-tomcat*, you have the running pod (build is finished, pod running) # EXEC: start the server adapter # ASSERT: RSync is executed and the output is visible in the "Console" Result: If you look closely at the output you see that the project is synced to the pod in a folder called *websocket-chat.jar* !console-output-1.png! Expected result: I should be able to set the output folder to anything I want. Ex. we have a customer that wants the application war to be synced up into a folder *ROOT* (without the extension *.war*). Currently, to achieve this I have to do the following: # EXEC: open the properties for the server adapter and hit "Switch Location" !switch-location.png! # ASSERT: in my workspace, a new project *Servers* is created. It contains the configuration for my server adapter. !server-adapter-configuration.png! # EXEC: open the file with the *XML Editor* and make sure it reads as follows: {code} <?xml version="1.0" encoding="UTF-8"?> <deployment> <local> <module id="org.eclipse.jst.jee.server:websocket-chat"> <property key="tempLocation" value="" /> <property key="location" value="" /> <property key="outputName" value="ROOT" /> </module> </local> </deployment> {code} # EXEC: html-encode and join it into a single line: # EXEC: go to the end of the line *<server auto-publish-setting="2"* and insert your html-encoded xml as a value to the attribute *org.jboss.ide.eclipse.as.core.util.deploymentPreferenceKey="* {code} <?xml version="1.0" encoding="UTF-8" standalone="no"?> <server auto-publish-setting="2" auto-publish-time="2" hostname="jboss-webserver31-tomcat-test.192.168.64.76.nip.io" id="test@jboss-webserver31-tomcat" id-set="true" name="jboss-webserver31-tomcat (Service) at OpenShift 3 (192.168.64.76)" org.jboss.ide.eclipse.as.core.server.IGNORE_LAUNCH_COMMANDS="true" org.jboss.ide.eclipse.as.core.server.deployDirectoryType="custom" org.jboss.ide.eclipse.as.core.server.serverMode="openshift3" org.jboss.ide.eclipse.as.core.server.webPort="80" org.jboss.ide.eclipse.as.core.server.webPortAutoDetect="false" org.jboss.ide.eclipse.as.core.server.zipDeploymentsPreference="true" org.jboss.tools.openshift.Connection="https://developer@192.168.64.76:8443" org.jboss.tools.openshift.DeployProject="websocket-chat" org.jboss.tools.openshift.PodPath="/opt/webserver/webapps" org.jboss.tools.openshift.SERVER_START_ON_CREATION="false" org.jboss.tools.openshift.Service="test@jboss-webserver31-tomcat" org.jboss.tools.openshift.SourcePath="${workspace_loc:/websocket-chat}" port="80" runtime-id="test@jboss-webserver31-tomcat" server-type="org.jboss.tools.openshift.server.type" server-type-id="org.jboss.tools.openshift.server.type" start-timeout="450" stop-timeout="450" timestamp="2" org.jboss.ide.eclipse.as.core.util.deploymentPreferenceKey="&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt; &lt;deployment&gt; &lt;local&gt; &lt;module id=&quot;org.eclipse.jst.jee.server:websocket-chat&quot;&gt; &lt;property key=&quot;tempLocation&quot; value=&quot;&quot; /&gt; &lt;property key=&quot;location&quot; value=&quot;&quot; /&gt; &lt;property key=&quot;outputName&quot; value=&quot;ROOT&quot; /&gt; &lt;/module&gt; &lt;/local&gt; &lt;/deployment&gt;"> <list key="modules" value0="websocket-chat::org.eclipse.jst.jee.server:websocket-chat::jst.web::3.0"/> </server> {code} # EXEC: Save the editor and restart the server Result: Syncing now happens into a folder *ROOT* !console-output-2.png! -- This message was sent by Atlassian Jira (v7.12.1#712002)