January 2019 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26533) Failed to get connectors from RemoteProxyWizardDiscoveryStrategy

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26533?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-26533: ---------------------------------- Steps to Reproduce: 1. download eclipse 2108-09 for java-ee developers. 2. Install eclipse (extract archive) 3. Install new software via http://download.jboss.org/jbosstools/photon/stable/updates/ 4. Assert: JBT are installed, and no error are in log view after eclipse restart Actual result: JBT are installed without issue, but there is this error in log view. > 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 > Reporter: Ondrej Dockal > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.11.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} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26533) Failed to get connectors from RemoteProxyWizardDiscoveryStrategy

by Ondrej Dockal (Jira)

Ondrej Dockal created JBIDE-26533: ------------------------------------- Summary: 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 Reporter: Ondrej Dockal Assignee: Jeff MAURY {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} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26532) Connection wizard: token is not updated after pasting login command with same server

by Josef Kopriva (Jira)

Josef Kopriva created JBIDE-26532: ------------------------------------- Summary: Connection wizard: token is not updated after pasting login command with same server Key: JBIDE-26532 URL: https://issues.jboss.org/browse/JBIDE-26532 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.11.0.AM1 Reporter: Josef Kopriva Assignee: Josef Kopriva Fix For: 4.11.0.AM1 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26530) Connection wizard: Login command with "_" in the token results in erroneous token being used

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26530?page=com.atlassian.jira.plugi... ] Josef Kopriva commented on JBIDE-26530: --------------------------------------- [~adietish] Thx! Also tokens with dashes does not work too, e.g. {code:java} oc login https://api.starter-us-east-2.openshift.com --token=12345-67890 {code} > Connection wizard: Login command with "_" in the token results in erroneous token being used > -------------------------------------------------------------------------------------------- > > Key: JBIDE-26530 > URL: https://issues.jboss.org/browse/JBIDE-26530 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.10.0.AM1 > Reporter: Andre Dietisheim > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.11.0.AM1 > > Attachments: image-2019-01-23-11-51-15-428.png > > > steps: > # ASSERT: copy the following login command into your clipboard: > {code}oc login https://api.starter-us-east-2.openshift.com --token=12345_67890{code} > # EXEC: in Eclipse: launch connection wizard > # EXEC: verify the token that's being used > Result: > The token that's being presented in the connection wizard ist *12345* > !image-2019-01-23-11-51-15-428.png! > Expected result: > The token that's being used should be *12345_67890* -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26531) Connection Wizard: Parse Login command do not parse correctly tokens

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26531?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-26531. --------------------------------- Resolution: Duplicate Issue > Connection Wizard: Parse Login command do not parse correctly tokens > -------------------------------------------------------------------- > > Key: JBIDE-26531 > URL: https://issues.jboss.org/browse/JBIDE-26531 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.11.0.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.11.0.AM1 > > > Some commands with token are not parsed correctly: > * tokens with underscore > * tokens with dashes -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26530) Connection wizard: Login command with "_" in the token results in erroneous token being used

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26530?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-26530: ---------------------------------- Fix Version/s: 4.11.0.AM1 (was: 4.11.x) > Connection wizard: Login command with "_" in the token results in erroneous token being used > -------------------------------------------------------------------------------------------- > > Key: JBIDE-26530 > URL: https://issues.jboss.org/browse/JBIDE-26530 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.10.0.AM1 > Reporter: Andre Dietisheim > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.11.0.AM1 > > Attachments: image-2019-01-23-11-51-15-428.png > > > steps: > # ASSERT: copy the following login command into your clipboard: > {code}oc login https://api.starter-us-east-2.openshift.com --token=12345_67890{code} > # EXEC: in Eclipse: launch connection wizard > # EXEC: verify the token that's being used > Result: > The token that's being presented in the connection wizard ist *12345* > !image-2019-01-23-11-51-15-428.png! > Expected result: > The token that's being used should be *12345_67890* -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[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 reassigned JBIDE-26529: ---------------------------------- Assignee: Jeff MAURY > 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.11.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)

7 years, 2 months

1
0
0 / 0

[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: ------------------------------- Fix Version/s: 4.11.0.AM1 > 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.11.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)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26529) Large Project Explorer tree causes editor input to lag

by Jesper Skov (Jira)

[ https://issues.jboss.org/browse/JBIDE-26529?page=com.atlassian.jira.plugi... ] Jesper Skov commented on JBIDE-26529: ------------------------------------- Easily reproducable with: Eclipse Java EE IDE for Web Developers. Version: 2018-09 (4.9.0) Build id: 20180917-1800 and java version "1.8.0_192" Java(TM) SE Runtime Environment (build 1.8.0_192-b12) Java HotSpot(TM) 64-Bit Server VM (build 25.192-b12, mixed mode) > 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 > Priority: Major > 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)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26531) Connection Wizard: Parse Login command do not parse correctly tokens

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26531?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-26531: ---------------------------------- Fix Version/s: 4.11.0.AM1 Story Points: 5 Sprint: devex #161 January 2019 > Connection Wizard: Parse Login command do not parse correctly tokens > -------------------------------------------------------------------- > > Key: JBIDE-26531 > URL: https://issues.jboss.org/browse/JBIDE-26531 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.11.0.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.11.0.AM1 > > > Some commands with token are not parsed correctly: > * tokens with underscore > * tokens with dashes -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2019