[JBoss JIRA] (JBIDE-17404) CordovaSim cannot be launched on RHEL7
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17404?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-17404:
------------------------------------------------
Karel, got any updates?
> CordovaSim cannot be launched on RHEL7
> --------------------------------------
>
> Key: JBIDE-17404
> URL: https://issues.jboss.org/browse/JBIDE-17404
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, browsersim
> Environment: RHEL7 latest, 64bit
> Installed webkitgtk3-devel 0:2.0.4-6-el7
> TicketMonster Cordava example from latest WFK
> JBDS 8.0.0.Beta1
> OpenJDK 7
> Reporter: Karel Piwko
> Assignee: Konstantin Marmalyukov
> Fix For: 4.2.0.Final
>
> Attachments: CordovaSimFailure.png, libwebkit2gtk.content, snapshot1.png, webkitgtk.content, webkitgtk3.content
>
>
> Launching BrowserSim fails with NPE, adding information from workspace log
> Before webkitgtk3-devel is installed
> {code}
> !ENTRY No engine information on the config.json, this is OK if using an old project. Falling back to default engine. 2 0 2014-05-23 13:03:54.128
> !MESSAGE org.jboss.tools.aerogear.hybrid.core
> !ENTRY org.jboss.tools.vpe.browsersim 4 0 2014-05-23 13:03:56.162
> !MESSAGE BrowserSim is failed to start with the following error:
> "No more handles"
> Please note that WebKitGTK 1.2.0 or newer must be installed and available in the library load path.
> If not, use your package manager to install libwebkitgtk.
> Also see <a href="https://community.jboss.org/docs/DOC-18100">BrowserSim FAQ</a>.
> Stack trace:
> org.eclipse.swt.SWTError: No more handles
> at org.eclipse.swt.SWT.error(SWT.java:4467)
> at org.eclipse.swt.SWT.error(SWT.java:4356)
> at org.eclipse.swt.SWT.error(SWT.java:4327)
> at org.eclipse.swt.browser.Browser.<init>(Browser.java:103)
> at org.jboss.tools.vpe.browsersim.browser.BrowserSimBrowser.<init>(BrowserSimBrowser.java:36)
> at org.jboss.tools.vpe.browsersim.browser.AbstractWebKitBrowser.<init>(AbstractWebKitBrowser.java:25)
> at org.jboss.tools.vpe.browsersim.browser.internal.WebKitBrowser_gtk_linux_x86_64.<init>(WebKitBrowser_gtk_linux_x86_64.java:37)
> at org.jboss.tools.vpe.browsersim.browser.WebKitBrowserFactory.createBrowser(WebKitBrowserFactory.java:39)
> at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.createCordovaSim(CordovaSimRunner.java:189)
> at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.startCordovaSim(CordovaSimRunner.java:90)
> at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.main(CordovaSimRunner.java:84)
> {code}
> After:
> {code}
> !ENTRY No engine information on the config.json, this is OK if using an old project. Falling back to default engine. 2 0 2014-05-23 14:03:57.380
> !MESSAGE org.jboss.tools.aerogear.hybrid.core
> !ENTRY No engine information on the config.json, this is OK if using an old project. Falling back to default engine. 2 0 2014-05-23 14:03:57.380
> !MESSAGE org.jboss.tools.aerogear.hybrid.core
> !ENTRY org.eclipse.core.jobs 4 2 2014-05-23 14:03:57.395
> !MESSAGE An internal error occurred during: "Launching TicketMonster-Cordova".
> !STACK 0
> java.lang.NullPointerException
> at org.jboss.tools.vpe.cordovasim.eclipse.launch.internal.CordovaSimLauncher.launchCordovaSim(CordovaSimLauncher.java:157)
> at org.jboss.tools.vpe.cordovasim.eclipse.launch.internal.CordovaSimLauncher.launchCordovaSim(CordovaSimLauncher.java:115)
> at org.jboss.tools.vpe.cordovasim.eclipse.launch.internal.CordovaSimLaunchConfigurationDelegate.launch(CordovaSimLaunchConfigurationDelegate.java:24)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:884)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBDS-3145) Computing connector status errors when loading the Software/Update tab of Central
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBDS-3145?page=com.atlassian.jira.plugin.... ]
Jiri Peterka commented on JBDS-3145:
------------------------------------
Seems its fixed, I've just tried that with JBDS 8.0.0.CR1a.
> Computing connector status errors when loading the Software/Update tab of Central
> ---------------------------------------------------------------------------------
>
> Key: JBDS-3145
> URL: https://issues.jboss.org/browse/JBDS-3145
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: discovery, updatesite
> Affects Versions: 8.0.0.CR1
> Reporter: Martin Malina
> Priority: Blocker
> Labels: respin-b
> Fix For: 8.0.0.CR1
>
>
> When I start JBDS and then go to the Software/Update tab of Central, the content starts loading and a few seconds later, these errors start popping up:
> {code}
> !ENTRY org.eclipse.core.jobs 4 2 2014-09-08 14:13:57.790
> !MESSAGE An internal error occurred during: "Computing connector status".
> !STACK 0
> java.lang.NullPointerException
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:101)
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:1)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:316)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> !ENTRY org.eclipse.core.jobs 4 2 2014-09-08 14:13:57.953
> !MESSAGE An internal error occurred during: "Computing connector status".
> !STACK 0
> java.lang.NullPointerException
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:101)
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:1)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:316)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> !ENTRY org.eclipse.core.jobs 4 2 2014-09-08 14:13:58.104
> !MESSAGE An internal error occurred during: "Computing connector status".
> !STACK 0
> java.lang.NullPointerException
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:101)
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:1)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:316)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> !ENTRY org.eclipse.core.jobs 4 2 2014-09-08 14:13:58.277
> !MESSAGE An internal error occurred during: "Computing connector status".
> !STACK 0
> java.lang.NullPointerException
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:101)
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:1)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:316)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> !ENTRY org.eclipse.core.jobs 4 2 2014-09-08 14:13:58.438
> !MESSAGE An internal error occurred during: "Computing connector status".
> !STACK 0
> java.lang.NullPointerException
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:101)
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:1)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:316)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> !ENTRY org.eclipse.core.jobs 4 2 2014-09-08 14:13:58.582
> !MESSAGE An internal error occurred during: "Computing connector status".
> !STACK 0
> java.lang.NullPointerException
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:101)
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:1)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:316)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> !ENTRY org.eclipse.core.jobs 4 2 2014-09-08 14:13:58.743
> !MESSAGE An internal error occurred during: "Computing connector status".
> !STACK 0
> java.lang.NullPointerException
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:101)
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:1)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:316)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> !ENTRY org.eclipse.core.jobs 4 2 2014-09-08 14:13:58.892
> !MESSAGE An internal error occurred during: "Computing connector status".
> !STACK 0
> java.lang.NullPointerException
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:101)
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:1)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:316)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> !ENTRY org.eclipse.core.jobs 4 2 2014-09-08 14:13:59.061
> !MESSAGE An internal error occurred during: "Computing connector status".
> !STACK 0
> java.lang.NullPointerException
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:101)
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:1)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:316)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> !ENTRY org.eclipse.core.jobs 4 2 2014-09-08 14:13:59.210
> !MESSAGE An internal error occurred during: "Computing connector status".
> !STACK 0
> java.lang.NullPointerException
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:101)
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:1)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:316)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> !ENTRY org.eclipse.core.jobs 4 2 2014-09-08 14:13:59.372
> !MESSAGE An internal error occurred during: "Computing connector status".
> !STACK 0
> java.lang.NullPointerException
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:101)
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:1)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:316)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> !ENTRY org.eclipse.core.jobs 4 2 2014-09-08 14:13:59.544
> !MESSAGE An internal error occurred during: "Computing connector status".
> !STACK 0
> java.lang.NullPointerException
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:101)
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:1)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:316)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> !ENTRY org.eclipse.core.jobs 4 2 2014-09-08 14:13:59.693
> !MESSAGE An internal error occurred during: "Computing connector status".
> !STACK 0
> java.lang.NullPointerException
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:101)
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:1)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:316)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> !ENTRY org.eclipse.core.jobs 4 2 2014-09-08 14:13:59.863
> !MESSAGE An internal error occurred during: "Computing connector status".
> !STACK 0
> java.lang.NullPointerException
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:101)
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:1)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:316)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
> It's not only in the log, but also shown as a popup window.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBDS-3145) Computing connector status errors when loading the Software/Update tab of Central
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-3145?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBDS-3145:
--------------------------------------
I believe this should be fixed now. Can you please retry?
> Computing connector status errors when loading the Software/Update tab of Central
> ---------------------------------------------------------------------------------
>
> Key: JBDS-3145
> URL: https://issues.jboss.org/browse/JBDS-3145
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: discovery, updatesite
> Affects Versions: 8.0.0.CR1
> Reporter: Martin Malina
> Priority: Blocker
> Labels: respin-b
> Fix For: 8.0.0.CR1
>
>
> When I start JBDS and then go to the Software/Update tab of Central, the content starts loading and a few seconds later, these errors start popping up:
> {code}
> !ENTRY org.eclipse.core.jobs 4 2 2014-09-08 14:13:57.790
> !MESSAGE An internal error occurred during: "Computing connector status".
> !STACK 0
> java.lang.NullPointerException
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:101)
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:1)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:316)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> !ENTRY org.eclipse.core.jobs 4 2 2014-09-08 14:13:57.953
> !MESSAGE An internal error occurred during: "Computing connector status".
> !STACK 0
> java.lang.NullPointerException
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:101)
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:1)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:316)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> !ENTRY org.eclipse.core.jobs 4 2 2014-09-08 14:13:58.104
> !MESSAGE An internal error occurred during: "Computing connector status".
> !STACK 0
> java.lang.NullPointerException
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:101)
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:1)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:316)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> !ENTRY org.eclipse.core.jobs 4 2 2014-09-08 14:13:58.277
> !MESSAGE An internal error occurred during: "Computing connector status".
> !STACK 0
> java.lang.NullPointerException
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:101)
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:1)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:316)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> !ENTRY org.eclipse.core.jobs 4 2 2014-09-08 14:13:58.438
> !MESSAGE An internal error occurred during: "Computing connector status".
> !STACK 0
> java.lang.NullPointerException
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:101)
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:1)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:316)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> !ENTRY org.eclipse.core.jobs 4 2 2014-09-08 14:13:58.582
> !MESSAGE An internal error occurred during: "Computing connector status".
> !STACK 0
> java.lang.NullPointerException
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:101)
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:1)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:316)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> !ENTRY org.eclipse.core.jobs 4 2 2014-09-08 14:13:58.743
> !MESSAGE An internal error occurred during: "Computing connector status".
> !STACK 0
> java.lang.NullPointerException
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:101)
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:1)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:316)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> !ENTRY org.eclipse.core.jobs 4 2 2014-09-08 14:13:58.892
> !MESSAGE An internal error occurred during: "Computing connector status".
> !STACK 0
> java.lang.NullPointerException
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:101)
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:1)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:316)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> !ENTRY org.eclipse.core.jobs 4 2 2014-09-08 14:13:59.061
> !MESSAGE An internal error occurred during: "Computing connector status".
> !STACK 0
> java.lang.NullPointerException
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:101)
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:1)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:316)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> !ENTRY org.eclipse.core.jobs 4 2 2014-09-08 14:13:59.210
> !MESSAGE An internal error occurred during: "Computing connector status".
> !STACK 0
> java.lang.NullPointerException
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:101)
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:1)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:316)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> !ENTRY org.eclipse.core.jobs 4 2 2014-09-08 14:13:59.372
> !MESSAGE An internal error occurred during: "Computing connector status".
> !STACK 0
> java.lang.NullPointerException
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:101)
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:1)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:316)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> !ENTRY org.eclipse.core.jobs 4 2 2014-09-08 14:13:59.544
> !MESSAGE An internal error occurred during: "Computing connector status".
> !STACK 0
> java.lang.NullPointerException
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:101)
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:1)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:316)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> !ENTRY org.eclipse.core.jobs 4 2 2014-09-08 14:13:59.693
> !MESSAGE An internal error occurred during: "Computing connector status".
> !STACK 0
> java.lang.NullPointerException
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:101)
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:1)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:316)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> !ENTRY org.eclipse.core.jobs 4 2 2014-09-08 14:13:59.863
> !MESSAGE An internal error occurred during: "Computing connector status".
> !STACK 0
> java.lang.NullPointerException
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:101)
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:1)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:316)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
> It's not only in the log, but also shown as a popup window.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-12108) BrowserSim is not visible when installed individually
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12108?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-12108:
-------------------------------------------
Assignee: Ilya Buziuk (was: Konstantin Marmalyukov)
> BrowserSim is not visible when installed individually
> ------------------------------------------------------
>
> Key: JBIDE-12108
> URL: https://issues.jboss.org/browse/JBIDE-12108
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 3.3.0.CR1
> Environment: JBT 3.3.0.CR1b, L64, Ubuntu 12.04
> Reporter: Jiri Peterka
> Assignee: Ilya Buziuk
> Fix For: 4.2.0.CR2
>
> Attachments: browsersim-enabled.png, customize-perspective.png, enable-browsersim.png, mobile-browser.bmp
>
>
> Unable to access BrowserSIM when installed as single feature from JBT CR1. Additional steps are required. This is confusing for a users. BrowserSIM should be accessible and visible after installation if possible.
> *These additional steps are:*
> # Right click on the Eclipse toolbar→Customize Perspective...:
> !customize-perspective.png!
> # Go to the Command Group Availability tab and select BrowserSim command group:
> !enable-browsersim.png!
> # BrowserSim icon will appear on the toolbar:
> !browsersim-enabled.png!
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18179) Forge Console is limited to 80 chars and throws exception if line surpasses the limit
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18179?page=com.atlassian.jira.plugi... ]
George Gastaldi updated JBIDE-18179:
------------------------------------
Labels: respin-b (was: )
> Forge Console is limited to 80 chars and throws exception if line surpasses the limit
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-18179
> URL: https://issues.jboss.org/browse/JBIDE-18179
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Reporter: George Gastaldi
> Assignee: George Gastaldi
> Priority: Blocker
> Labels: respin-b
> Fix For: 4.2.0.CR1
>
>
> {code}
> org.eclipse.jface.text.BadLocationException
> at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1179)
> at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1210)
> at org.jboss.tools.aesh.ui.internal.document.DocumentImpl$3.run(DocumentImpl.java:103)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3806)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3444)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18258) "Cannot find navigator content extension" when starting a local server after setting up a remote server
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18258?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-18258:
------------------------------------------
I tried the issue while using the binaries of respin-a. It also worked flawlessly, I could not see the error described above. Puzzled...
> "Cannot find navigator content extension" when starting a local server after setting up a remote server
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18258
> URL: https://issues.jboss.org/browse/JBIDE-18258
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx, server
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.2.0.CR1
>
>
> When I set up a local server, then a remote server and then I start the local server, I get errors:
> {code}
> !ENTRY org.eclipse.ui.navigator 4 0 2014-09-04 11:46:26.700
> !MESSAGE Cannot find navigator content extension (using triggerPoints) for object "org.jboss.modules.Main [22362]" parent path: "R/". Check that you have an expression for this object in a navigatorContent triggerPoints or enablement.
> !ENTRY org.eclipse.ui.navigator 4 0 2014-09-04 11:46:26.703
> !MESSAGE Cannot find navigator content extension (using triggerPoints) for object "org.jboss.modules.Main [22362]" parent path: "R/". Check that you have an expression for this object in a navigatorContent triggerPoints or enablement.
> !ENTRY org.eclipse.ui.navigator 4 0 2014-09-04 11:46:26.895
> !MESSAGE Cannot find navigator content extension (using triggerPoints) for object "org.jboss.modules.Main [22362]" parent path: "R/". Check that you have an expression for this object in a navigatorContent triggerPoints or enablement.
> {code}
> I'm not exactly sure how this works, but strangely, the errors are thrown even after I remove the remote server. But they did not occur before I created the remote server. So perhaps it has something to do with the existence of the remote system and not really the remote server itself? I don't know.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months