[
https://issues.jboss.org/browse/JBIDE-21294?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-21294:
---------------------------------------
[~fbricon], yes, that's what I realized when I saw the field empty.
So there are two issues:
1. Why is vagrant location empty when it worked for me in other instances?
2. Why is there am ugly NPE if it's empty? There should be a basic check if the field
is empty.
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
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)