[JBoss JIRA] (JBIDE-26158) Server adapter: NPE when starting adapter into Debug
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26158?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26158:
-------------------------------------
Priority: Major (was: Critical)
> Server adapter: NPE when starting adapter into Debug
> -----------------------------------------------------
>
> Key: JBIDE-26158
> URL: https://issues.jboss.org/browse/JBIDE-26158
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: upstream
> Fix For: 4.9.0.AM1
>
> Attachments: image-2018-07-02-22-33-13-396.png, image-2018-07-02-22-49-45-246.png, image-2018-07-02-23-17-34-099.png, image-2018-07-03-00-03-56-346.png, screenshot-1.png, screenshot-2.png
>
>
> steps:
> # EXEC: launch new application wizard, choose nodejs-mongo-persistent template and finish
> # EXEC: when asked import the app and create a server adapter
> # ASSERT: server adapter is created
> # EXEC: start the server adapter
> # ASSERT: server adapter is launched
> # EXEC: restart the server adapter into Debug
> Result:
> Debuggin works, but you get the following error dialog:
> !image-2018-07-02-22-33-13-396.png!
> In the Eclipse log you'll find the following:
> {code}
> java.lang.NullPointerException
> at org.eclipse.core.internal.resources.CheckMissingNaturesListener.updateRange(CheckMissingNaturesListener.java:209)
> at org.eclipse.core.internal.resources.CheckMissingNaturesListener$3.runInWorkspace(CheckMissingNaturesListener.java:179)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
> {code}
> ps. project context menu: Convert > Javascript Project doesn't help.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26160) Server Adapter: erroneously keeps being in Debugging when you kill the pod
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-26160:
----------------------------------------
Summary: Server Adapter: erroneously keeps being in Debugging when you kill the pod
Key: JBIDE-26160
URL: https://issues.jboss.org/browse/JBIDE-26160
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.6.0.AM3
Reporter: Andre Dietisheim
steps:
# EXEC: create an application (via ex. nodejs-mongo-persistent template), import the project and create a server adapter for it
# ASSERT: server adapter is created
# EXEC: start the server adapter in Debugging
# ASSERT: sever adapter is in *[Debugging, Synchronized]* state
# ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is started
# EXEC: in Explorer: select the pod for your service and pick "Delete"
# ASSERT: pod gets deleted and recreated
# ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is stopped
Result:
The server adapter still says that is is *[Debugging, Synchronized]*, but debugging is not working any more. The new pod is not running in debug (dev-) mode any more. To have it running again you need to restart the server adapter into debug, which will re-create a new pod in debug-mode.
Expected result:
Server adapter should get out of debugging and back into normal run mode.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26160) Server Adapter: erroneously keeps being in Debugging when you kill the pod
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26160?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26160:
-------------------------------------
Labels: server_adapter (was: )
> Server Adapter: erroneously keeps being in Debugging when you kill the pod
> --------------------------------------------------------------------------
>
> Key: JBIDE-26160
> URL: https://issues.jboss.org/browse/JBIDE-26160
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Labels: server_adapter
>
> steps:
> # EXEC: create an application (via ex. nodejs-mongo-persistent template), import the project and create a server adapter for it
> # ASSERT: server adapter is created
> # EXEC: start the server adapter in Debugging
> # ASSERT: sever adapter is in *[Debugging, Synchronized]* state
> # ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is started
> # EXEC: in Explorer: select the pod for your service and pick "Delete"
> # ASSERT: pod gets deleted and recreated
> # ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is stopped
> Result:
> The server adapter still says that is is *[Debugging, Synchronized]*, but debugging is not working any more. The new pod is not running in debug (dev-) mode any more. To have it running again you need to restart the server adapter into debug, which will re-create a new pod in debug-mode.
> Expected result:
> Server adapter should get out of debugging and back into normal run mode.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26159) Server adapter: debugging is not stopped if you delete the pod
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26159?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26159:
-------------------------------------
Labels: port_forwarding server_adapter (was: )
> Server adapter: debugging is not stopped if you delete the pod
> --------------------------------------------------------------
>
> Key: JBIDE-26159
> URL: https://issues.jboss.org/browse/JBIDE-26159
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Priority: Minor
> Labels: port_forwarding, server_adapter
> Fix For: 4.9.x
>
>
> steps:
> Screencast: https://youtu.be/XMA--S9zj6s
> # EXEC: create an application (via ex. nodejs-mongo-persistent template)
> # ASSERT: pod for service is running
> # EXEC: select pod and pick "Port Forwarding..." and start the forwarding
> # ASSERT: forwarding is running
> # EXEC: verify on the cmd-line that the forwarding is running
> {code}
> $ ps ax | grep oc
> 47793 ?? S 0:00.25 /Users/adietish/Downloads/oc_341 port-forward --token=XXXXX --server=https://open.paas.redhat.com --insecure-skip-tls-verify=true -n jbide25000 -p nodejs-mongo-persistent-7-rsmlr 5858:5858 8080:8080
> {code}
> # EXEC: in Explorer: select the pod for your service and pick "Delete"
> # ASSERT: pod gets deleted and recreated
> # EXEC: verify on the cmd-line that the forwarding is running
> {code}
> $ ps ax | grep oc
> 47793 ?? S 0:00.25 /Users/adietish/Downloads/oc_341 port-forward --token=XXXXX --server=https://open.paas.redhat.com --insecure-skip-tls-verify=true -n jbide25000 -p nodejs-mongo-persistent-7-rsmlr 5858:5858 8080:8080
> {code}
> Result:
> The port forwarding is still running.
> In Eclipse there's no way for you to see this since you have to select the new pod and pick "Port Forwarding..." on this new pod. It'll then tell you that the port forwarding is *NOT* running, since we're asking about port-forwarding for the new pod (not the old one that was killed).
> PS. it looks like there's a timeout somewhere, oc stops port-forwarding at some point (many minutes later) and the process disappears.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26159) Server adapter: debugging is not stopped if you delete the pod
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26159?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26159:
-------------------------------------
Description:
steps:
Screencast: https://youtu.be/XMA--S9zj6s
# EXEC: create an application (via ex. nodejs-mongo-persistent template)
# ASSERT: pod for service is running
# EXEC: select pod and pick "Port Forwarding..." and start the forwarding
# ASSERT: forwarding is running
# EXEC: verify on the cmd-line that the forwarding is running
{code}
$ ps ax | grep oc
47793 ?? S 0:00.25 /Users/adietish/Downloads/oc_341 port-forward --token=XXXXX --server=https://open.paas.redhat.com --insecure-skip-tls-verify=true -n jbide25000 -p nodejs-mongo-persistent-7-rsmlr 5858:5858 8080:8080
{code}
# EXEC: in Explorer: select the pod for your service and pick "Delete"
# ASSERT: pod gets deleted and recreated
# EXEC: verify on the cmd-line that the forwarding is running
{code}
$ ps ax | grep oc
47793 ?? S 0:00.25 /Users/adietish/Downloads/oc_341 port-forward --token=XXXXX --server=https://open.paas.redhat.com --insecure-skip-tls-verify=true -n jbide25000 -p nodejs-mongo-persistent-7-rsmlr 5858:5858 8080:8080
{code}
Result:
The port forwarding is still running.
In Eclipse there's no way for you to see this since you have to select the new pod and pick "Port Forwarding..." on this new pod. It'll then tell you that the port forwarding is *NOT* running, since we're asking about port-forwarding for the new pod (not the old one that was killed).
PS. it looks like there's a timeout somewhere, oc stops port-forwarding at some point (many minutes later) and the process disappears.
was:
steps:
# EXEC: create an application (via ex. nodejs-mongo-persistent template)
# ASSERT: pod for service is running
# EXEC: select pod and pick "Port Forwarding..." and start the forwarding
# ASSERT: forwarding is running
# EXEC: verify on the cmd-line that the forwarding is running
{code}
$ ps ax | grep oc
47793 ?? S 0:00.25 /Users/adietish/Downloads/oc_341 port-forward --token=XXXXX --server=https://open.paas.redhat.com --insecure-skip-tls-verify=true -n jbide25000 -p nodejs-mongo-persistent-7-rsmlr 5858:5858 8080:8080
{code}
# EXEC: in Explorer: select the pod for your service and pick "Delete"
# ASSERT: pod gets deleted and recreated
# EXEC: verify on the cmd-line that the forwarding is running
{code}
$ ps ax | grep oc
47793 ?? S 0:00.25 /Users/adietish/Downloads/oc_341 port-forward --token=XXXXX --server=https://open.paas.redhat.com --insecure-skip-tls-verify=true -n jbide25000 -p nodejs-mongo-persistent-7-rsmlr 5858:5858 8080:8080
{code}
Result:
The port forwarding is still running.
In Eclipse there's no way for you to see this since you have to select the new pod and pick "Port Forwarding..." on this new pod. It'll then tell you that the port forwarding is *NOT* running, since we're asking about port-forwarding for the new pod (not the old one that was killed).
PS. it looks like there's a timeout somewhere, oc stops port-forwarding at some point (many minutes later) and the process disappears.
> Server adapter: debugging is not stopped if you delete the pod
> --------------------------------------------------------------
>
> Key: JBIDE-26159
> URL: https://issues.jboss.org/browse/JBIDE-26159
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Priority: Minor
> Fix For: 4.9.x
>
>
> steps:
> Screencast: https://youtu.be/XMA--S9zj6s
> # EXEC: create an application (via ex. nodejs-mongo-persistent template)
> # ASSERT: pod for service is running
> # EXEC: select pod and pick "Port Forwarding..." and start the forwarding
> # ASSERT: forwarding is running
> # EXEC: verify on the cmd-line that the forwarding is running
> {code}
> $ ps ax | grep oc
> 47793 ?? S 0:00.25 /Users/adietish/Downloads/oc_341 port-forward --token=XXXXX --server=https://open.paas.redhat.com --insecure-skip-tls-verify=true -n jbide25000 -p nodejs-mongo-persistent-7-rsmlr 5858:5858 8080:8080
> {code}
> # EXEC: in Explorer: select the pod for your service and pick "Delete"
> # ASSERT: pod gets deleted and recreated
> # EXEC: verify on the cmd-line that the forwarding is running
> {code}
> $ ps ax | grep oc
> 47793 ?? S 0:00.25 /Users/adietish/Downloads/oc_341 port-forward --token=XXXXX --server=https://open.paas.redhat.com --insecure-skip-tls-verify=true -n jbide25000 -p nodejs-mongo-persistent-7-rsmlr 5858:5858 8080:8080
> {code}
> Result:
> The port forwarding is still running.
> In Eclipse there's no way for you to see this since you have to select the new pod and pick "Port Forwarding..." on this new pod. It'll then tell you that the port forwarding is *NOT* running, since we're asking about port-forwarding for the new pod (not the old one that was killed).
> PS. it looks like there's a timeout somewhere, oc stops port-forwarding at some point (many minutes later) and the process disappears.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26159) Server adapter: debugging is not stopped if you delete the pod
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26159?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26159:
-------------------------------------
Description:
steps:
# EXEC: create an application (via ex. nodejs-mongo-persistent template)
# ASSERT: pod for service is running
# EXEC: select pod and pick "Port Forwarding..." and start the forwarding
# ASSERT: forwarding is running
# EXEC: verify on the cmd-line that the forwarding is running
{code}
$ ps ax | grep oc
47793 ?? S 0:00.25 /Users/adietish/Downloads/oc_341 port-forward --token=XXXXX --server=https://open.paas.redhat.com --insecure-skip-tls-verify=true -n jbide25000 -p nodejs-mongo-persistent-7-rsmlr 5858:5858 8080:8080
{code}
# EXEC: in Explorer: select the pod for your service and pick "Delete"
# ASSERT: pod gets deleted and recreated
# EXEC: verify on the cmd-line that the forwarding is running
{code}
$ ps ax | grep oc
47793 ?? S 0:00.25 /Users/adietish/Downloads/oc_341 port-forward --token=XXXXX --server=https://open.paas.redhat.com --insecure-skip-tls-verify=true -n jbide25000 -p nodejs-mongo-persistent-7-rsmlr 5858:5858 8080:8080
{code}
Result:
The port forwarding is still running.
In Eclipse there's no way for you to see this since you have to select the new pod and pick "Port Forwarding..." on this new pod. It'll then tell you that the port forwarding is *NOT* running, since we're asking about port-forwarding for the new pod (not the old one that was killed).
PS. it looks like there's a timeout somewhere, oc stops port-forwarding at some point (many minutes later) and the process disappears.
was:
steps:
# EXEC: create an application (via ex. nodejs-mongo-persistent template)
# ASSERT: pod for service is running
# EXEC: select pod and pick "Port Forwarding..." and start the forwarding
# ASSERT: forwarding is running
# EXEC: verify on the cmd-line that the forwarding is running
{code}
$ ps ax | grep oc
47793 ?? S 0:00.25 /Users/adietish/Downloads/oc_341 port-forward --token=XXXXX --server=https://open.paas.redhat.com --insecure-skip-tls-verify=true -n jbide25000 -p nodejs-mongo-persistent-7-rsmlr 5858:5858 8080:8080
{code}
# EXEC: in Explorer: select the pod for your service and pick "Delete"
# ASSERT: pod gets deleted and recreated
# EXEC: verify on the cmd-line that the forwarding is running
{code}
$ ps ax | grep oc
47793 ?? S 0:00.25 /Users/adietish/Downloads/oc_341 port-forward --token=XXXXX --server=https://open.paas.redhat.com --insecure-skip-tls-verify=true -n jbide25000 -p nodejs-mongo-persistent-7-rsmlr 5858:5858 8080:8080
{code}
Result:
The port forwarding is still running.
In Eclipse there's no way for you to see this since you have to select the new pod and pick "Port Forwarding..." on this new pod. It'll then tell you that the port forwarding is *NOT* running, since we're asking about port-forwarding for the new pod (not the old one that was killed).
PS. it looks like there's a timeout somewhere, oc stops port-forwarding at some point (many minutes later) and the process disappears.
> Server adapter: debugging is not stopped if you delete the pod
> --------------------------------------------------------------
>
> Key: JBIDE-26159
> URL: https://issues.jboss.org/browse/JBIDE-26159
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Priority: Minor
> Fix For: 4.9.x
>
>
> steps:
> # EXEC: create an application (via ex. nodejs-mongo-persistent template)
> # ASSERT: pod for service is running
> # EXEC: select pod and pick "Port Forwarding..." and start the forwarding
> # ASSERT: forwarding is running
> # EXEC: verify on the cmd-line that the forwarding is running
> {code}
> $ ps ax | grep oc
> 47793 ?? S 0:00.25 /Users/adietish/Downloads/oc_341 port-forward --token=XXXXX --server=https://open.paas.redhat.com --insecure-skip-tls-verify=true -n jbide25000 -p nodejs-mongo-persistent-7-rsmlr 5858:5858 8080:8080
> {code}
> # EXEC: in Explorer: select the pod for your service and pick "Delete"
> # ASSERT: pod gets deleted and recreated
> # EXEC: verify on the cmd-line that the forwarding is running
> {code}
> $ ps ax | grep oc
> 47793 ?? S 0:00.25 /Users/adietish/Downloads/oc_341 port-forward --token=XXXXX --server=https://open.paas.redhat.com --insecure-skip-tls-verify=true -n jbide25000 -p nodejs-mongo-persistent-7-rsmlr 5858:5858 8080:8080
> {code}
> Result:
> The port forwarding is still running.
> In Eclipse there's no way for you to see this since you have to select the new pod and pick "Port Forwarding..." on this new pod. It'll then tell you that the port forwarding is *NOT* running, since we're asking about port-forwarding for the new pod (not the old one that was killed).
> PS. it looks like there's a timeout somewhere, oc stops port-forwarding at some point (many minutes later) and the process disappears.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26159) Server adapter: debugging is not stopped if you delete the pod
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-26159:
----------------------------------------
Summary: Server adapter: debugging is not stopped if you delete the pod
Key: JBIDE-26159
URL: https://issues.jboss.org/browse/JBIDE-26159
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.6.0.AM3
Reporter: Andre Dietisheim
Priority: Minor
steps:
# EXEC: create an application (via ex. nodejs-mongo-persistent template)
# ASSERT: pod for service is running
# EXEC: select pod and pick "Port Forwarding..." and start the forwarding
# ASSERT: forwarding is running
# EXEC: verify on the cmd-line that the forwarding is running
{code}
$ ps ax | grep oc
47793 ?? S 0:00.25 /Users/adietish/Downloads/oc_341 port-forward --token=XXXXX --server=https://open.paas.redhat.com --insecure-skip-tls-verify=true -n jbide25000 -p nodejs-mongo-persistent-7-rsmlr 5858:5858 8080:8080
{code}
# EXEC: in Explorer: select the pod for your service and pick "Delete"
# ASSERT: pod gets deleted and recreated
# EXEC: verify on the cmd-line that the forwarding is running
{code}
$ ps ax | grep oc
47793 ?? S 0:00.25 /Users/adietish/Downloads/oc_341 port-forward --token=XXXXX --server=https://open.paas.redhat.com --insecure-skip-tls-verify=true -n jbide25000 -p nodejs-mongo-persistent-7-rsmlr 5858:5858 8080:8080
{code}
Result:
The port forwarding is still running.
In Eclipse there's no way for you to see this since you have to select the new pod and pick "Port Forwarding..." on this new pod. It'll then tell you that the port forwarding is *NOT* running, since we're asking about port-forwarding for the new pod (not the old one that was killed).
PS. it looks like there's a timeout somewhere, oc stops port-forwarding at some point (many minutes later) and the process disappears.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26159) Server adapter: debugging is not stopped if you delete the pod
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26159?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26159:
-------------------------------------
Fix Version/s: 4.9.x
> Server adapter: debugging is not stopped if you delete the pod
> --------------------------------------------------------------
>
> Key: JBIDE-26159
> URL: https://issues.jboss.org/browse/JBIDE-26159
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Priority: Minor
> Fix For: 4.9.x
>
>
> steps:
> # EXEC: create an application (via ex. nodejs-mongo-persistent template)
> # ASSERT: pod for service is running
> # EXEC: select pod and pick "Port Forwarding..." and start the forwarding
> # ASSERT: forwarding is running
> # EXEC: verify on the cmd-line that the forwarding is running
> {code}
> $ ps ax | grep oc
> 47793 ?? S 0:00.25 /Users/adietish/Downloads/oc_341 port-forward --token=XXXXX --server=https://open.paas.redhat.com --insecure-skip-tls-verify=true -n jbide25000 -p nodejs-mongo-persistent-7-rsmlr 5858:5858 8080:8080
> {code}
> # EXEC: in Explorer: select the pod for your service and pick "Delete"
> # ASSERT: pod gets deleted and recreated
> # EXEC: verify on the cmd-line that the forwarding is running
> {code}
> $ ps ax | grep oc
> 47793 ?? S 0:00.25 /Users/adietish/Downloads/oc_341 port-forward --token=XXXXX --server=https://open.paas.redhat.com --insecure-skip-tls-verify=true -n jbide25000 -p nodejs-mongo-persistent-7-rsmlr 5858:5858 8080:8080
> {code}
> Result:
> The port forwarding is still running.
> In Eclipse there's no way for you to see this since you have to select the new pod and pick "Port Forwarding..." on this new pod. It'll then tell you that the port forwarding is *NOT* running, since we're asking about port-forwarding for the new pod (not the old one that was killed).
> PS. it looks like there's a timeout somewhere, oc stops port-forwarding at some point (many minutes later) and the process disappears.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26158) Server adapter: NPE when starting adapter into Debug
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26158?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-26158:
----------------------------------------
Assignee: Andre Dietisheim
> Server adapter: NPE when starting adapter into Debug
> -----------------------------------------------------
>
> Key: JBIDE-26158
> URL: https://issues.jboss.org/browse/JBIDE-26158
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: upstream
> Fix For: 4.9.0.AM1
>
> Attachments: image-2018-07-02-22-33-13-396.png, image-2018-07-02-22-49-45-246.png, image-2018-07-02-23-17-34-099.png, image-2018-07-03-00-03-56-346.png, screenshot-1.png, screenshot-2.png
>
>
> steps:
> # EXEC: launch new application wizard, choose nodejs-mongo-persistent template and finish
> # EXEC: when asked import the app and create a server adapter
> # ASSERT: server adapter is created
> # EXEC: start the server adapter
> # ASSERT: server adapter is launched
> # EXEC: restart the server adapter into Debug
> Result:
> Debuggin works, but you get the following error dialog:
> !image-2018-07-02-22-33-13-396.png!
> In the Eclipse log you'll find the following:
> {code}
> java.lang.NullPointerException
> at org.eclipse.core.internal.resources.CheckMissingNaturesListener.updateRange(CheckMissingNaturesListener.java:209)
> at org.eclipse.core.internal.resources.CheckMissingNaturesListener$3.runInWorkspace(CheckMissingNaturesListener.java:179)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
> {code}
> ps. project context menu: Convert > Javascript Project doesn't help.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months