[
https://issues.jboss.org/browse/JBIDE-21904?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-21904:
------------------------------------------
[~scabanovich] yes I agree, this is thightly related to JBIDE-21830 and JBIDE-21858.
I'll include the fixes for this and the other issues in a single PR.
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.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)