[
https://issues.jboss.org/browse/JBIDE-14630?page=com.atlassian.jira.plugi...
]
Andre Dietisheim updated JBIDE-14630:
-------------------------------------
Steps to Reproduce:
# ASSERT: make sure that you have at least 1 connection with 1 application
# EXEC: from OpenShift Explorer pick *Create Server Adapter*
# EXEC: in the upcoming wizard hit *Browse* and set the deployment folder to some custom
value, hit *Finish*
# EXEC: open freshly created server adapter in editor and check what deployment folder is
displayed
Result:
The output folder is not the custom folder you've chosen
Expected result:
The output folder matches the custom folder you've set in the wizard
was:
# ASSERT: make sure that you have at least 1 connection with 2 different applications: 1x
jbossas-7 and 1x jbossews-2
# EXEC: from OpenShift Explorer pick *Create Server Adapter* on the jbossas-7 application
# ASSERT: in the upcoming wizard the jbossas-7 application is selected
# ASSERT: the output-directory is *deployments*
# EXEC: switch the application combo to the jbossews-2 application
Result:
The output folder is still *deployments*
Expected result:
The output folder switches to *webapps*
The above steps of course also work the other way round if you switch from jbossews-2 to
jbossas-7
server adapter wizard: custom deploy folder is not set to adapter
that is created
---------------------------------------------------------------------------------
Key: JBIDE-14630
URL:
https://issues.jboss.org/browse/JBIDE-14630
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 4.1.0.Beta1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira