[
https://jira.jboss.org/browse/JBIDE-7296?page=com.atlassian.jira.plugin.s...
]
Rob Stryker commented on JBIDE-7296:
------------------------------------
I've made a commit here so that new servers get all required attributes set. I
targeted it to this bug because I think it's relevant. I'm not sure how to
replicate your specific bug. When I create a new server and start a remote, I no longer
get any errors after this recent commit. But my error was different than that one.
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