[
https://jira.jboss.org/browse/JBIDE-7187?page=com.atlassian.jira.plugin.s...
]
Max Andersen commented on JBIDE-7187:
-------------------------------------
Two things:
1) you *can* create an additonal remote server - no one says you need to use your local
one. We need the local part (the runtime) to provide access to a classpath.
2) As discussed per mail/chat what should be done is that the new server wizard should
have the option on wether it is local/remote in the server wizard and not only as a second
step.
3) We will eventually also have a deploy only server that does not have any ties at all to
your local server but then things becomes harder to verify/check.
Publishing to remote server is counter-intuitive
------------------------------------------------
Key: JBIDE-7187
URL:
https://jira.jboss.org/browse/JBIDE-7187
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Affects Versions: 3.2.0.M2
Reporter: Pete Muir
Assignee: Rob Stryker
This approach of "changing" your local server to be a remote server is very odd
and counter-intuitive. My remote server is not some version of a local server, it's a
whole different server. I would much prefer to create a new remote server.
Strongly recommend you revisit this UI design, it's going to cause a lot of WTF
moments ;-)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira