[
https://jira.jboss.org/jira/browse/JBIDE-5187?page=com.atlassian.jira.plu...
]
Rob Stryker commented on JBIDE-5187:
------------------------------------
I do not think the runtime makes sense at all. If your remote server is using JBoss 5.2,
and you have a local JBoss 5.2 handy, your runtime type should be of type "JBoss
5.2" and not type "SSH Server Runtime".
So in this case you'd create a "JBoss 5.2" runtime, and an SSH server. It
would be redundant to create a "JBoss 5.2" runtime, then create a "JBoss
SSH Server Runtime" which delegates to the "JBoss 5.2 runtime", and then
create a "JBoss SSH Server" object. Only the 5.2 runtime and the ssh server
should be created. The ssh runtime serves no purpose. All projects would then target the
local 5.2 runtime.
As for why it's not yet a functionality of the common types, I've been busy and
have not gotten to that yet. There are API constraints currently which I'm
investigating ways to get around.
SSH Runtime has no icon in JBoss Community group.
-------------------------------------------------
Key: JBIDE-5187
URL:
https://jira.jboss.org/jira/browse/JBIDE-5187
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.1.0.CR1
Reporter: Anton Klimkovich
Assignee: Rob Stryker
Priority: Minor
Fix For: 3.1.0.CR1
EXECUTE: Preferences-> Server-> Runtime Environments
EXECUTE: press Add button
EXECUTE: Select JBoss Community group
FAILURE: SSH Runtime has no icon
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira