[
https://issues.jboss.org/browse/JBIDE-21065?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-21065:
-------------------------------------
This bug has more problems than you'd expect. Here's another workflow that's
failing:
1) Open new server wizard
2) leave host as localhost, click next
3) Click "server lifecycle is externally managed" so it is now
'checked'
4) click back
5) Change host to your ip address
6) Click next
7) Note that the checkbox is still checked for externally managed
8) complete the wizard normally
9) Open server editor
10) note 'externally managed' is not checked.
In short, wtp constantly calling 'setDefaults' will reset many of our settings.
Server host name address should not be defaulted during server
adapter creation
-------------------------------------------------------------------------------
Key: JBIDE-21065
URL:
https://issues.jboss.org/browse/JBIDE-21065
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.3.0.Final
Reporter: Xavier Coulon
I've noticed that when I create a server adapter and I give it an IP address as the
hostname, the hostname remains the default value, ie, {{localhost}}.
This is annoying in the case where I want to connect to a VM running on my own host (eg,
a VM running Docker). In this particular case, I set the hostname at something like
{{192.168.99.100}} but it is reverted as {{localhost}} which gives {{127.0.0.1}} as the
primary IP address. As a consequence, the server adapter fails to connect to the server
since it uses the wrong IP address.
Note that the host name can be changed for good in the Server Configuration Editor
_after_ its creation.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)