[jbosstools-issues] [JBoss JIRA] (JBIDE-21904) Pod deployment path is not reflecting selected service

[Andre Dietisheim (JIRA)]

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

Andre Dietisheim commented on JBIDE-21904:
------------------------------------------

we do not infer the deployment path in the wizard any more. We just allow the user to tellt the server adapter to automatically determine (infer) the deployment path when publishing. We're are not displaying it in the wizard any more. This is highly beneficial to the startup time reported in JBIDE-21858. 
Thus this issue went obsolete.

> Pod deployment path is not reflecting selected service
> ------------------------------------------------------
>
>                 Key: JBIDE-21904
>                 URL: https://issues.jboss.org/browse/JBIDE-21904
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.3.1.CR1
>            Reporter: Marián Labuda
>            Assignee: Andre Dietisheim
>             Fix For: 4.3.1.CR1
>
>
> Having more services under an OpenShift 3 connection and trying to create a new OS 3 server adapter does not use correct pod deployment path in following scenario:
> I am having a project with eap application (created from eap 64 basic s2i) and nodejs application. When I select nodejs application /opt/apt-root/src is used as a Pod Deployment Path. After selecting an EAP service, Pod Deployment Path is changed to /opt/eap/standalone/deployments. When I select nodejs in this point, Pod Deployment Path is not updated again and value is still /opt/eap/standalone/deployments, what is wrong.
> # ASSERT: have a project with 2 services (eap-app, nodejs-example)
> # EXEC: launch new OpenShift 3 Server Adapter wizard
> # EXEC: select nodejs-example service 
> # ASSERT: "Pod Deployment Path" is set to */opt/apt-root/src*
> # EXEC: select eap-app service
> # ASSERT: "Pod Deployment Path" is set to */opt/eap/standalone/deployments*
> # EXEC: select nodejs-example service
> Result:
> "Pod Deployment Path" is still */opt/apt-root/src*
> Expected Result:
> "Pod Deployment Path" should be set to */opt/eap/standalone/deployments*



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)