[
https://issues.jboss.org/browse/JBIDE-9913?page=com.atlassian.jira.plugin...
]
Rodney Russ commented on JBIDE-9913:
------------------------------------
Martin, Snjezana had the following to say about testing this:
"I had to change the JBoss AS Runtime detector because of changes in JBIDE-9913. In
order to test the changes it would be enough to start JBDS with EAP. If EAP is created
correctly, this issue is fixed."
Is that enough for you to verify?
NPE on start and publish of servers
-----------------------------------
Key: JBIDE-9913
URL:
https://issues.jboss.org/browse/JBIDE-9913
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Reporter: Max Rydahl Andersen
Assignee: Snjezana Peco
Priority: Blocker
Fix For: 3.3.0.M4
Currently breaking the builds and any usage of any server:
!ENTRY org.eclipse.core.jobs 4 2 2011-10-13 23:25:40.580
!MESSAGE An internal error occurred during: "Starting
org.jboss.ide.eclipse.as.42".
!STACK 0
java.lang.NullPointerException
at
org.jboss.ide.eclipse.as.core.server.internal.BehaviourModel.getLaunchDelegate(BehaviourModel.java:61)
at
org.jboss.ide.eclipse.as.core.server.internal.launch.DelegatingStartLaunchConfiguration.getDelegate(DelegatingStartLaunchConfiguration.java:47)
at
org.jboss.ide.eclipse.as.core.server.internal.launch.DelegatingStartLaunchConfiguration.preLaunchCheck(DelegatingStartLaunchConfiguration.java:61)
at
org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:809)
at
org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703)
at
org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:696)
at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3402)
at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3340)
at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:363)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira