[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-7296) Remote System Deployment: classToLaunch cannot be null

[Max Andersen (JIRA)]

     [ https://jira.jboss.org/browse/JBIDE-7296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Max Andersen updated JBIDE-7296:
--------------------------------

    Fix Version/s: 3.2.0.Beta2
         Priority: Blocker  (was: Major)


Burr, did you do this on a newly instance in the server view or on an old existing one ?

About ssh key you need to be a tad more specific, it's like any other ssh key and only need to be done once (I.e. Add it to the ssh preference). Suggestions on how to do it better (and still secure) are welcome. 

> Remote System Deployment: classToLaunch cannot be null
> ------------------------------------------------------
>
>                 Key: JBIDE-7296
>                 URL: https://jira.jboss.org/browse/JBIDE-7296
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Archives
>         Environment: Win7 Java 1.6 32-bit JVM and JBDS 4.0 M2
>            Reporter: Burr Sutter
>            Assignee: Rob Stryker
>            Priority: Blocker
>             Fix For: 3.2.0.Beta2
>
>         Attachments: RemoteServer_Start_Error.png, Server_Setup_Tab.png
>
>
> Selecting Start on the Server results in:
> An internal error occurred during: "Starting JBoss 6.0 M5 Remote Server".
> classToLaunch cannot be null
> See screenshots

-- 
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