[jbosstools-issues] [JBoss JIRA] (JBIDE-21294) NPE when starting CDK server
Rob Stryker (JIRA)
issues at jboss.org
Thu Dec 10 18:31:00 EST 2015
[ https://issues.jboss.org/browse/JBIDE-21294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Stryker resolved JBIDE-21294.
---------------------------------
Resolution: Done
I've fixed the NPE at least. This still doesn't solve why you can't find the vagrant command, but my improvements in error messaging instruct user to look at their path and modify it.
> NPE when starting CDK server
> ----------------------------
>
> Key: JBIDE-21294
> URL: https://issues.jboss.org/browse/JBIDE-21294
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta1
>
>
> I've been testing the CDK adapter with [1] today and when I tried to start again from scratch (vagrant destroy + new workspace) and added the server again and started, I got a NPE:
> {code}
> An internal error occurred during: "Starting cdk-v2 CDK Server".
> java.lang.NullPointerException
> at java.io.File.<init>(File.java:277)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.launch(CDKLaunchController.java:133)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
> I did add the user credentials in the server editor.
> Now I looked in the launch config and the first field at the top is empty - it should contain path to vagrant. I'm not sure why it's missing - I just used runtime detection. But in any case, the NPE should be handled somehow.
> [1] https://github.com/redhat-developer-tooling/openshift-vagrant
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jbosstools-issues
mailing list