[JBoss JIRA] (JBIDE-21067) Error Log view is polluted with NullPointerExceptions when debugging JavaScript with ChromeDevTools
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21067?page=com.atlassian.jira.plugi... ]
Denis Golovin reassigned JBIDE-21067:
-------------------------------------
Assignee: Viacheslav Kabanovich
> Error Log view is polluted with NullPointerExceptions when debugging JavaScript with ChromeDevTools
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21067
> URL: https://issues.jboss.org/browse/JBIDE-21067
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common/jst/core
> Affects Versions: 4.3.0.Final, 4.4.0.Alpha1
> Reporter: Denis Golovin
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.0.Alpha1
>
>
> When debugging JavaScript with ChromeDevTools for Java it creates special project inside current workspace and populate it with .js files using eclipse file system (EFS) API. IReource instance for .js file inside project returns null if requested for location through IResource.getLocation() method. null is valid return value according to JavaDoc for the method.
> Now JBossTools code fails with NullPointerException and pollutes Error Log View
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.common.model.util.EclipseResourceUtil.createObjectForResource(EclipseResourceUtil.java:368)
> at org.jboss.tools.jst.web.ui.navigator.XContentProvider.hasChildren(XContentProvider.java:96)
> at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.hasChildren(SafeDelegateTreeContentProvider.java:112)
> at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.callNormalHasChildren(NavigatorContentServiceContentProvider.java:444)
> at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.access$4(NavigatorContentServiceContentProvider.java:439)
> at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider$3.run(NavigatorContentServiceContentProvider.java:407)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.hasChildren(NavigatorContentServiceContentProvider.java:392)
> at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.hasChildren(NavigatorContentServiceContentProvider.java:436)
> at org.eclipse.jface.viewers.AbstractTreeViewer.isExpandable(AbstractTreeViewer.java:2124)
> at org.eclipse.jface.viewers.TreeViewer.isExpandable(TreeViewer.java:538)
> at org.eclipse.jface.viewers.AbstractTreeViewer.isExpandable(AbstractTreeViewer.java:2162)
> at org.eclipse.jface.viewers.AbstractTreeViewer.updatePlus(AbstractTreeViewer.java:2844)
> at org.eclipse.jface.viewers.TreeViewer.updatePlus(TreeViewer.java:786)
> at org.eclipse.jface.viewers.AbstractTreeViewer.createTreeItem(AbstractTreeViewer.java:840)
> at org.eclipse.jface.viewers.AbstractTreeViewer.lambda$0(AbstractTreeViewer.java:816)
> at org.eclipse.jface.viewers.AbstractTreeViewer$$Lambda$43/10378869.run(Unknown Source)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:791)
> at org.eclipse.jface.viewers.TreeViewer.createChildren(TreeViewer.java:596)
> at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:762)
> at org.eclipse.jface.viewers.AbstractTreeViewer.handleTreeExpand(AbstractTreeViewer.java:1489)
> at org.eclipse.jface.viewers.TreeViewer.handleTreeExpand(TreeViewer.java:882){code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21067) Error Log view is polluted with NullPointerExceptions when debugging JavaScript with ChromeDevTools
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21067?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-21067:
----------------------------------
Fix Version/s: 4.4.0.Alpha1
> Error Log view is polluted with NullPointerExceptions when debugging JavaScript with ChromeDevTools
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21067
> URL: https://issues.jboss.org/browse/JBIDE-21067
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common/jst/core
> Affects Versions: 4.3.0.Final, 4.4.0.Alpha1
> Reporter: Denis Golovin
> Fix For: 4.4.0.Alpha1
>
>
> When debugging JavaScript with ChromeDevTools for Java it creates special project inside current workspace and populate it with .js files using eclipse file system (EFS) API. IReource instance for .js file inside project returns null if requested for location through IResource.getLocation() method. null is valid return value according to JavaDoc for the method.
> Now JBossTools code fails with NullPointerException and pollutes Error Log View
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.common.model.util.EclipseResourceUtil.createObjectForResource(EclipseResourceUtil.java:368)
> at org.jboss.tools.jst.web.ui.navigator.XContentProvider.hasChildren(XContentProvider.java:96)
> at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.hasChildren(SafeDelegateTreeContentProvider.java:112)
> at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.callNormalHasChildren(NavigatorContentServiceContentProvider.java:444)
> at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.access$4(NavigatorContentServiceContentProvider.java:439)
> at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider$3.run(NavigatorContentServiceContentProvider.java:407)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.hasChildren(NavigatorContentServiceContentProvider.java:392)
> at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.hasChildren(NavigatorContentServiceContentProvider.java:436)
> at org.eclipse.jface.viewers.AbstractTreeViewer.isExpandable(AbstractTreeViewer.java:2124)
> at org.eclipse.jface.viewers.TreeViewer.isExpandable(TreeViewer.java:538)
> at org.eclipse.jface.viewers.AbstractTreeViewer.isExpandable(AbstractTreeViewer.java:2162)
> at org.eclipse.jface.viewers.AbstractTreeViewer.updatePlus(AbstractTreeViewer.java:2844)
> at org.eclipse.jface.viewers.TreeViewer.updatePlus(TreeViewer.java:786)
> at org.eclipse.jface.viewers.AbstractTreeViewer.createTreeItem(AbstractTreeViewer.java:840)
> at org.eclipse.jface.viewers.AbstractTreeViewer.lambda$0(AbstractTreeViewer.java:816)
> at org.eclipse.jface.viewers.AbstractTreeViewer$$Lambda$43/10378869.run(Unknown Source)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:791)
> at org.eclipse.jface.viewers.TreeViewer.createChildren(TreeViewer.java:596)
> at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:762)
> at org.eclipse.jface.viewers.AbstractTreeViewer.handleTreeExpand(AbstractTreeViewer.java:1489)
> at org.eclipse.jface.viewers.TreeViewer.handleTreeExpand(TreeViewer.java:882){code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21067) Error Log view is polluted with NullPointerExceptions when debugging JavaScript with ChromeDevTools
by Denis Golovin (JIRA)
Denis Golovin created JBIDE-21067:
-------------------------------------
Summary: Error Log view is polluted with NullPointerExceptions when debugging JavaScript with ChromeDevTools
Key: JBIDE-21067
URL: https://issues.jboss.org/browse/JBIDE-21067
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: common/jst/core
Affects Versions: 4.3.0.Final, 4.4.0.Alpha1
Reporter: Denis Golovin
When debugging JavaScript with ChromeDevTools for Java it creates special project inside current workspace and populate it with .js files using eclipse file system (EFS) API. IReource instance for .js file inside project returns null if requested for location through IResource.getLocation() method. null is valid return value according to JavaDoc for the method.
Now JBossTools code fails with NullPointerException and pollutes Error Log View
{code}
java.lang.NullPointerException
at org.jboss.tools.common.model.util.EclipseResourceUtil.createObjectForResource(EclipseResourceUtil.java:368)
at org.jboss.tools.jst.web.ui.navigator.XContentProvider.hasChildren(XContentProvider.java:96)
at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.hasChildren(SafeDelegateTreeContentProvider.java:112)
at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.callNormalHasChildren(NavigatorContentServiceContentProvider.java:444)
at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.access$4(NavigatorContentServiceContentProvider.java:439)
at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider$3.run(NavigatorContentServiceContentProvider.java:407)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.hasChildren(NavigatorContentServiceContentProvider.java:392)
at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.hasChildren(NavigatorContentServiceContentProvider.java:436)
at org.eclipse.jface.viewers.AbstractTreeViewer.isExpandable(AbstractTreeViewer.java:2124)
at org.eclipse.jface.viewers.TreeViewer.isExpandable(TreeViewer.java:538)
at org.eclipse.jface.viewers.AbstractTreeViewer.isExpandable(AbstractTreeViewer.java:2162)
at org.eclipse.jface.viewers.AbstractTreeViewer.updatePlus(AbstractTreeViewer.java:2844)
at org.eclipse.jface.viewers.TreeViewer.updatePlus(TreeViewer.java:786)
at org.eclipse.jface.viewers.AbstractTreeViewer.createTreeItem(AbstractTreeViewer.java:840)
at org.eclipse.jface.viewers.AbstractTreeViewer.lambda$0(AbstractTreeViewer.java:816)
at org.eclipse.jface.viewers.AbstractTreeViewer$$Lambda$43/10378869.run(Unknown Source)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:791)
at org.eclipse.jface.viewers.TreeViewer.createChildren(TreeViewer.java:596)
at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:762)
at org.eclipse.jface.viewers.AbstractTreeViewer.handleTreeExpand(AbstractTreeViewer.java:1489)
at org.eclipse.jface.viewers.TreeViewer.handleTreeExpand(TreeViewer.java:882){code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21005) Node / Bower / npm location should point to the node executable file instead of the parent folder of it
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21005?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-21005:
-------------------------------------
[~psrna], np ;-)
Basically it's ready for nightly builds - we will start CQ with the code that is in master right now
> Node / Bower / npm location should point to the node executable file instead of the parent folder of it
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21005
> URL: https://issues.jboss.org/browse/JBIDE-21005
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: javascript, nodejs
> Affects Versions: 4.3.0.Final
> Reporter: Alexey Kazakov
> Assignee: Ilya Buziuk
> Fix For: 4.4.0.Alpha1
>
>
> Window->Preferences->Java Script tools->Node
> It's confusing that "Node Location" in that preference page is actually references to the parent folder of the executable node file. I would expect "/usr/bin/nodejs" or "C:/.../node.exe" in that field.
> IMO it's confusing and actually not very flexible. Why wouldn't let users to select the executable file itself?
> WDYT?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21005) Node / Bower / npm location should point to the node executable file instead of the parent folder of it
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21005?page=com.atlassian.jira.plugi... ]
Pavol Srna commented on JBIDE-21005:
------------------------------------
[~ibuziuk], thanks for the heads up on this jira. Sure I can test on nightly when ready ...
> Node / Bower / npm location should point to the node executable file instead of the parent folder of it
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21005
> URL: https://issues.jboss.org/browse/JBIDE-21005
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: javascript, nodejs
> Affects Versions: 4.3.0.Final
> Reporter: Alexey Kazakov
> Assignee: Ilya Buziuk
> Fix For: 4.4.0.Alpha1
>
>
> Window->Preferences->Java Script tools->Node
> It's confusing that "Node Location" in that preference page is actually references to the parent folder of the executable node file. I would expect "/usr/bin/nodejs" or "C:/.../node.exe" in that field.
> IMO it's confusing and actually not very flexible. Why wouldn't let users to select the executable file itself?
> WDYT?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21049) Add "wildfly-messaging-activemq-deployment_1_0.xsd" to xml catalog
by Wolfgang Knauf (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21049?page=com.atlassian.jira.plugi... ]
Wolfgang Knauf commented on JBIDE-21049:
----------------------------------------
Also missing: "jboss-web_10_0.xsd"
> Add "wildfly-messaging-activemq-deployment_1_0.xsd" to xml catalog
> ------------------------------------------------------------------
>
> Key: JBIDE-21049
> URL: https://issues.jboss.org/browse/JBIDE-21049
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: server
> Affects Versions: 4.3.0.Final
> Reporter: Wolfgang Knauf
> Assignee: Rob Stryker
> Priority: Minor
>
> WildFly 10 introduced a new schema "wildfly-messaging-activemq-deployment_1_0.xsd" for configuration of e.g. an ActiveMQ queue as part of a deployable archive, e.g. an EAR file (a file with the extension "...-jms.xml").
> This schema file is missing in the XSD catalog.
> Here is a sample xml instance:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <messaging-deployment xmlns="urn:jboss:messaging-activemq-deployment:1.0">
> <server>
> <jms-destinations>
> <jms-queue name="MessageBeanQueue">
> <entry name="jms/queue/MessageBeanQueue"/>
> </jms-queue>
> </jms-destinations>
> </server>
> </messaging-deployment>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21005) Node / Bower / npm location should point to the node executable file instead of the parent folder of it
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21005?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-21005:
-------------------------------------
[~akazakov], sounds good. I also have some suggestions that we can discuss later (will write it here in order not to forget):
1) We might use ${system_path} for Linux - it seems to work neatly there
2) We might have issues on Mac, cause there might be nothing concrete in system path (desktop launch case). So we could detect tools in default locations:
- usr/bin
- usr/local/bin
- usr/local/bower
- usr/local/npm
etc..
{quote}
Windows code should be smart enough to distinguish one from another and use "/path/to/node.exe /path/to/npm.cli.js" or "/path/to/npm.cmd" depending on the preference setting for the npm bin file.
{quote}
Yes, this is a good idea indeed. However, need to think how to implement it neatly and in a generic way - launching npm / bower *directly* breaks architecture of launching everything via node (launch that is not depend on path). But I anyways I do believe that user experience is more important than architecture to a certain extend
> Node / Bower / npm location should point to the node executable file instead of the parent folder of it
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21005
> URL: https://issues.jboss.org/browse/JBIDE-21005
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: javascript, nodejs
> Affects Versions: 4.3.0.Final
> Reporter: Alexey Kazakov
> Assignee: Ilya Buziuk
> Fix For: 4.4.0.Alpha1
>
>
> Window->Preferences->Java Script tools->Node
> It's confusing that "Node Location" in that preference page is actually references to the parent folder of the executable node file. I would expect "/usr/bin/nodejs" or "C:/.../node.exe" in that field.
> IMO it's confusing and actually not very flexible. Why wouldn't let users to select the executable file itself?
> WDYT?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21066) Extra step in opening terminal in git perspective?
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21066?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21066:
-----------------------------------
Project: Tools (JBoss Tools) (was: Developer Studio (JBoss Developer Studio))
Key: JBIDE-21066 (was: JBDS-3507)
Workflow: GIT Pull Request workflow (was: CDW v1)
Status: Open (was: New)
Docs QE Status: (was: NEW)
Component/s: upstream
(was: 3rd-party-dependencies)
(was: upstream)
(was: 3rd-party-certification)
Target Release: (was: 9.0.0.GA)
Affects Version/s: 4.3.0.Final
(was: 9.0.0.Beta2)
Fix Version/s: 4.3.1.Final
4.4.0.Alpha1
(was: 9.1.0.GA)
(was: 10.0.0.Alpha1)
> Extra step in opening terminal in git perspective?
> --------------------------------------------------
>
> Key: JBIDE-21066
> URL: https://issues.jboss.org/browse/JBIDE-21066
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.3.0.Final
> Reporter: Len DiMaggio
> Assignee: Daniel Azarov
> Fix For: 4.3.1.Final, 4.4.0.Alpha1
>
> Attachments: terminal.png
>
>
> If a user opens a terminal view from the git perspective - for example, by performing "show in" for a local repo, an empty terminal view is displayed. The user must then click on the terminal icon to actually open the terminal. This seems like an extra step - why wouldn't we open a terminal when we open the terminal view?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21066) Extra step in opening terminal in git perspective?
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21066?page=com.atlassian.jira.plugi... ]
Alexey Kazakov resolved JBIDE-21066.
------------------------------------
Resolution: Done
Thanks!
> Extra step in opening terminal in git perspective?
> --------------------------------------------------
>
> Key: JBIDE-21066
> URL: https://issues.jboss.org/browse/JBIDE-21066
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.3.0.Final
> Reporter: Len DiMaggio
> Assignee: Daniel Azarov
> Fix For: 4.3.1.Final, 4.4.0.Alpha1
>
> Attachments: terminal.png
>
>
> If a user opens a terminal view from the git perspective - for example, by performing "show in" for a local repo, an empty terminal view is displayed. The user must then click on the terminal icon to actually open the terminal. This seems like an extra step - why wouldn't we open a terminal when we open the terminal view?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBDS-3507) Extra step in opening terminal in git perspective?
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3507?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3507:
---------------------------------
Fix Version/s: 9.1.0.GA
10.0.0.Alpha1
(was: 9.x)
(was: 10.x)
> Extra step in opening terminal in git perspective?
> --------------------------------------------------
>
> Key: JBDS-3507
> URL: https://issues.jboss.org/browse/JBDS-3507
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: 3rd-party-certification, 3rd-party-dependencies, upstream
> Affects Versions: 9.0.0.Beta2
> Reporter: Len DiMaggio
> Assignee: Daniel Azarov
> Fix For: 9.1.0.GA, 10.0.0.Alpha1
>
> Attachments: terminal.png
>
>
> If a user opens a terminal view from the git perspective - for example, by performing "show in" for a local repo, an empty terminal view is displayed. The user must then click on the terminal icon to actually open the terminal. This seems like an extra step - why wouldn't we open a terminal when we open the terminal view?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months