[JBoss JIRA] (JBIDE-26529) Large Project Explorer tree causes editor input to lag
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26529?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26529:
-------------------------------
Sprint: devex #164 April 2019, devex #165 April 2019 (was: devex #164 April 2019)
> Large Project Explorer tree causes editor input to lag
> ------------------------------------------------------
>
> Key: JBIDE-26529
> URL: https://issues.jboss.org/browse/JBIDE-26529
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jst
> Affects Versions: 4.9.0.Final
> Environment: Java 11, Eclipse 2019.03 JEE, Windows 7
> Reporter: Jesper Skov
> Assignee: Jeff MAURY
> Priority: Major
> Fix For: 4.12.0.AM1
>
> Attachments: eclipse-bug-jboss.zip
>
>
> We use JBoss Tools with Eclipse JEE distribution.
> When Projetc Explorer contains a large tree (small elevator), performance of the java editor gets really bad with frequent lags.
> I have first reported it as a problem against native Eclipse (https://bugs.eclipse.org/bugs/show_bug.cgi?id=543678) but it turns out the problem can only be reproduced when the feature 'org.jboss.tools.jst.feature.feature.group' is installed.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 12 months
[JBoss JIRA] (ERT-690) [GTK4] Adapt to new drawing model changes [EBZ#540674]
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/ERT-690?page=com.atlassian.jira.plugin.sy... ]
Jeff MAURY updated ERT-690:
---------------------------
Sprint: devex #159 December 2018, devex #161 January 2019, devex #162 February 2019, devex #163 March 2019, devex #164 April 2019, devex #165 April 2019 (was: devex #159 December 2018, devex #161 January 2019, devex #162 February 2019, devex #163 March 2019, devex #164 April 2019)
> [GTK4] Adapt to new drawing model changes [EBZ#540674]
> ------------------------------------------------------
>
> Key: ERT-690
> URL: https://issues.jboss.org/browse/ERT-690
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Platform
> Reporter: Friendly Jira Robot
> Assignee: Eric Williams
> Priority: Major
> Labels: SWT, bzira
>
> The "draw" signal is gone, use snapshots instead.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 12 months
[JBoss JIRA] (JBIDE-26533) Failed to get connectors from RemoteProxyWizardDiscoveryStrategy
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26533?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26533:
-------------------------------
Sprint: devex #164 April 2019, devex #165 April 2019 (was: devex #164 April 2019)
> Failed to get connectors from RemoteProxyWizardDiscoveryStrategy
> ----------------------------------------------------------------
>
> Key: JBIDE-26533
> URL: https://issues.jboss.org/browse/JBIDE-26533
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 4.9.0.Final
> Environment: Fedora 29, Eclipse 2018-09, Eclipse 2018-12
> Reporter: Ondrej Dockal
> Assignee: Jeff MAURY
> Priority: Critical
> Fix For: 4.12.0.AM1
>
>
> {code}
> eclipse.buildId=4.9.0.I20180906-0745
> java.version=1.8.0_191
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product org.eclipse.epp.package.jee.product
> Command-line arguments: -data file:/home/odockal/eclipse-workspace-jee-2018-09/ -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product
> org.eclipse.mylyn.discovery.core
> Error
> Wed Jan 23 14:52:17 CET 2019
> Failed to get connectors from RemoteProxyWizardDiscoveryStrategy
> java.lang.NullPointerException
> at java.net.URI$Parser.parse(URI.java:3042)
> at java.net.URI.<init>(URI.java:588)
> at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy.loadRegistry(RemoteExternalBundleDiscoveryStrategy.java:91)
> at org.jboss.tools.discovery.core.internal.connectors.xpl.ExternalBundleDiscoveryStrategy.performDiscovery(ExternalBundleDiscoveryStrategy.java:117)
> at org.jboss.tools.discovery.core.internal.connectors.ChainedDiscoveryStrategy.performDiscovery(ChainedDiscoveryStrategy.java:68)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:116)
> at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardManager.loadWizards(ProxyWizardManager.java:107)
> at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardUpdateJob.run(ProxyWizardUpdateJob.java:47)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
> {code}
> {code}
> eclipse.buildId=4.9.0.I20180906-0745
> java.version=1.8.0_191
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product org.eclipse.epp.package.jee.product
> Command-line arguments: -data file:/home/odockal/eclipse-workspace-jee-2018-09/ -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product
> org.jboss.tools.discovery.core
> Error
> Wed Jan 23 14:52:17 CET 2019
> No URL set for discovery catalog. Property jboss.discovery.directory.url is missing!
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 12 months
[JBoss JIRA] (ERT-681) [GTK] Port SWT to GTK4 [EBZ#540385]
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/ERT-681?page=com.atlassian.jira.plugin.sy... ]
Jeff MAURY updated ERT-681:
---------------------------
Sprint: devex #157 November 2019, devex #158 November 2018, devex #159 December 2018, devex #161 January 2019, devex #162 February 2019, devex #163 March 2019, devex #164 April 2019, devex #165 April 2019 (was: devex #157 November 2019, devex #158 November 2018, devex #159 December 2018, devex #161 January 2019, devex #162 February 2019, devex #163 March 2019, devex #164 April 2019)
> [GTK] Port SWT to GTK4 [EBZ#540385]
> -----------------------------------
>
> Key: ERT-681
> URL: https://issues.jboss.org/browse/ERT-681
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Platform
> Reporter: Friendly Jira Robot
> Assignee: Eric Williams
> Priority: Major
> Labels: SWT, bzira
>
> Umbrella bug for any porting work related to GTK4.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 12 months
[JBoss JIRA] (JBDS-4735) Central projects Wizard sometimes fails to open
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBDS-4735?page=com.atlassian.jira.plugin.... ]
Jeff MAURY updated JBDS-4735:
-----------------------------
Sprint: devex #159 December 2018, devex #161 January 2019, devex #162 February 2019, devex #163 March 2019, devex #164 April 2019, devex #165 April 2019 (was: devex #159 December 2018, devex #161 January 2019, devex #162 February 2019, devex #163 March 2019, devex #164 April 2019)
> Central projects Wizard sometimes fails to open
> -----------------------------------------------
>
> Key: JBDS-4735
> URL: https://issues.jboss.org/browse/JBDS-4735
> Project: Red Hat CodeReady Studio (devstudio)
> Issue Type: Bug
> Components: central
> Affects Versions: 12.9.0.GA
> Environment: manually Fedora 28, automation
> Reporter: Vojtech Prusa
> Assignee: Jeff MAURY
> Priority: Major
> Fix For: 12.12.0.AM1
>
> Attachments: central.tar.gz, image-2018-10-17-09-24-31-555.png, screenshot-1.png
>
>
> There is "openInIDE" used in 3 places in "main.min.js" in central source code*. When the central reloads and works normally, "openInIDE" is a function (probably defined in Java code or somewhere out of the "main.min.js" file) with following implementation:
> function openInIDE() {
> var result = callJava(1, '9aee3b4a3f3b40ed26f47d66375b25e3', Array.prototype.slice.call(arguments));
> if (typeof result == 'string' && result.indexOf('org.eclipse.swt.browser.error') == 0) {
> var error = new Error(result.substring(29));
> throw error;
> }
> return result;
> }
> After the issue appears, "typedef openInIDE" is undefined, which causes probably the issues.
> *Additional information to the 3 places, where "openInIDE" appears - it appears in 2 functions:
> - registerButtonClicks() - here is the "openInIDE" needed for loading and displaying the central correctly
> - delegateToIDE(a, b) - here is the "openInIDE" needed for opening the wizard to the quickstart
> OLDER DESCRIPTION (does not describes the issue enough, but I decided to keep it for more details about the issue):
> ----------------------------------------------------------------------------------------------------------------------
> Sometimes central examples wizards fail to load and modal dialog is shown instead (screen attached).
> Nothing in Error log view.
> Restarting devstudio solves the issue.
> Adding screen and central tar of:
> devstudio-12.9.0.GA-v20180928-1629-B3448/workspaces/workspace/.metadata/.plugins/org.jboss.tools.central/central
> Addition info:
> Considering that central itests fails for this sometimes fresh installation without restart may cause this. Although it happen again after running devstudio for some time and restarting Central view.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 12 months
[JBoss JIRA] (ERT-624) Triage SWT GTK bugs
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/ERT-624?page=com.atlassian.jira.plugin.sy... ]
Jeff MAURY updated ERT-624:
---------------------------
Sprint: devex #149 May 2018, devex #151 June 2018, devex #153 August 2018, devex #155 September 2018, devex #156 October 2018, devex #157 November 2019, devex #158 November 2018, devex #159 December 2018, devex #161 January 2019, devex #162 February 2019, devex #163 March 2019, devex #164 April 2019, devex #165 April 2019 (was: devex #149 May 2018, devex #151 June 2018, devex #153 August 2018, devex #155 September 2018, devex #156 October 2018, devex #157 November 2019, devex #158 November 2018, devex #159 December 2018, devex #161 January 2019, devex #162 February 2019, devex #163 March 2019, devex #164 April 2019)
> Triage SWT GTK bugs
> -------------------
>
> Key: ERT-624
> URL: https://issues.jboss.org/browse/ERT-624
> Project: Eclipse Release Train
> Issue Type: Task
> Reporter: Eric Williams
> Assignee: Eric Williams
> Priority: Minor
>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 12 months