[jbosstools-issues] [JBoss JIRA] (JBIDE-14037) NPE during launch change notification

Max Rydahl Andersen (JIRA) jira-events at lists.jboss.org
Fri Apr 19 10:43:53 EDT 2013


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

Max Rydahl Andersen updated JBIDE-14037:
----------------------------------------

    Fix Version/s: 4.1.0.Beta1
                       (was: 4.1.0.Alpha2)

    
> NPE during launch change notification
> -------------------------------------
>
>                 Key: JBIDE-14037
>                 URL: https://issues.jboss.org/browse/JBIDE-14037
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: forge
>    Affects Versions: 4.1.0.Alpha1
>            Reporter: Pavol Srna
>            Assignee: Koen Aers
>             Fix For: 4.1.0.Beta1
>
>         Attachments: forge_pref.png
>
>
> This problem occurred when I tried to uncheck already active/selected runtime in forge preferences. 
> A possible solution could be that the embedded runtime would be selected when unchecking already active forge runtime.
> Exception:
> {code}
> java.lang.NullPointerException
> 	at org.jboss.tools.forge.core.process.ForgeLaunchHelper$ForgeLaunchListener.launchRemoved(ForgeLaunchHelper.java:184)
> 	at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.run(LaunchManager.java:443)
> 	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> 	at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.notify(LaunchManager.java:428)
> 	at org.eclipse.debug.internal.core.LaunchManager.fireUpdate(LaunchManager.java:1017)
> 	at org.eclipse.debug.internal.core.LaunchManager.removeLaunch(LaunchManager.java:2224)
> 	at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationManager.removeTerminatedLaunches(LaunchConfigurationManager.java:329)
> 	at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationManager.launchAdded(LaunchConfigurationManager.java:315)
> 	at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.run(LaunchManager.java:440)
> 	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> 	at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.notify(LaunchManager.java:428)
> 	at org.eclipse.debug.internal.core.LaunchManager.fireUpdate(LaunchManager.java:1017)
> 	at org.eclipse.debug.internal.core.LaunchManager.addLaunch(LaunchManager.java:688)
> 	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:844)
> 	at org.jboss.tools.forge.core.process.ForgeLaunchHelper.doLaunch(ForgeLaunchHelper.java:69)
> 	at org.jboss.tools.forge.core.process.ForgeLaunchHelper.launch(ForgeLaunchHelper.java:53)
> 	at org.jboss.tools.forge.core.process.ForgeAbstractRuntime.start(ForgeAbstractRuntime.java:50)
> 	at org.jboss.tools.forge.ui.util.ForgeHelper$1.run(ForgeHelper.java:41)
> 	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jbosstools-issues mailing list