August 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24785) No URL set for discovery catalog

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24785?page=com.atlassian.jira.plugi... ] Lukáš Valach commented on JBIDE-24785: -------------------------------------- There is possible PR: https://github.com/jbosstools/jbosstools-download.jboss.org/pull/627 But I don't know how to test if it solve this issue. [~nickboldt], could you merge and rebuild what necessary please? > No URL set for discovery catalog > -------------------------------- > > Key: JBIDE-24785 > URL: https://issues.jboss.org/browse/JBIDE-24785 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central > Affects Versions: 4.5.0.Final > Reporter: Lukáš Valach > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.5.0.Final > > > I installed eclipse-jee-oxygen-R-linux-gtk-x86_64 \[1\] and then "Abridged JBoss Tools" from update site \[2\]. I see these errors in eclipse log: > {code} > !ENTRY org.jboss.tools.discovery.core 4 0 2017-08-01 10:27:25.641 > !MESSAGE No URL set for discovery catalog. Property jboss.discovery.directory.url is missing! > !ENTRY org.jboss.tools.discovery.core 4 0 2017-08-01 10:27:26.751 > !MESSAGE No URL set for discovery catalog. Property jboss.discovery.directory.url is missing! > !ENTRY org.jboss.tools.discovery.core 4 0 2017-08-01 10:27:26.756 > !MESSAGE All attempts to discover connectors have failed > !SUBENTRY 1 org.eclipse.mylyn.discovery.core 4 0 2017-08-01 10:27:26.756 > !MESSAGE Failed to get connectors from RemoteProxyWizardDiscoveryStrategy > !STACK 0 > 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:56) > {code} > It seems that there is mistake in ide-config.properties \[3\]. Last snapshot version should be 4.5.0.Final, but is 4.5.0.GA. > \[1\] https://www.eclipse.org/downloads/download.php?file=/technology/epp/downl... > \[2\] http://download.jboss.org/jbosstools/oxygen/snapshots/updates/ > \[3\] http://download.jboss.org/jbosstools/configuration/ide-config.properties -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24785) No URL set for discovery catalog

by Lukáš Valach (JIRA)

Lukáš Valach created JBIDE-24785: ------------------------------------ Summary: No URL set for discovery catalog Key: JBIDE-24785 URL: https://issues.jboss.org/browse/JBIDE-24785 Project: Tools (JBoss Tools) Issue Type: Bug Components: build, central Affects Versions: 4.5.0.Final Reporter: Lukáš Valach Assignee: Nick Boldt Priority: Critical Fix For: 4.5.0.Final I installed eclipse-jee-oxygen-R-linux-gtk-x86_64 \[1\] and then "Abridged JBoss Tools" from update site \[2\]. I see these errors in eclipse log: {code} !ENTRY org.jboss.tools.discovery.core 4 0 2017-08-01 10:27:25.641 !MESSAGE No URL set for discovery catalog. Property jboss.discovery.directory.url is missing! !ENTRY org.jboss.tools.discovery.core 4 0 2017-08-01 10:27:26.751 !MESSAGE No URL set for discovery catalog. Property jboss.discovery.directory.url is missing! !ENTRY org.jboss.tools.discovery.core 4 0 2017-08-01 10:27:26.756 !MESSAGE All attempts to discover connectors have failed !SUBENTRY 1 org.eclipse.mylyn.discovery.core 4 0 2017-08-01 10:27:26.756 !MESSAGE Failed to get connectors from RemoteProxyWizardDiscoveryStrategy !STACK 0 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:56) {code} It seems that there is mistake in ide-config.properties \[3\]. Last snapshot version should be 4.5.0.Final, but is 4.5.0.GA. \[1\] https://www.eclipse.org/downloads/download.php?file=/technology/epp/downl... \[2\] http://download.jboss.org/jbosstools/oxygen/snapshots/updates/ \[3\] http://download.jboss.org/jbosstools/configuration/ide-config.properties -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24775) Token field isn't automatically filled in after token extraction

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24775?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-24775: ---------------------------------- Assignee: Andre Dietisheim > Token field isn't automatically filled in after token extraction > ---------------------------------------------------------------- > > Key: JBIDE-24775 > URL: https://issues.jboss.org/browse/JBIDE-24775 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Dmitrii Bocharov > Assignee: Andre Dietisheim > Fix For: 4.5.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24775) Token field isn't automatically filled in after token extraction

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24775?page=com.atlassian.jira.plugi... ] Jeff MAURY resolved JBIDE-24775. -------------------------------- Resolution: Done > Token field isn't automatically filled in after token extraction > ---------------------------------------------------------------- > > Key: JBIDE-24775 > URL: https://issues.jboss.org/browse/JBIDE-24775 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Dmitrii Bocharov > Fix For: 4.5.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24775) Token field isn't automatically filled in after token extraction

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24775?page=com.atlassian.jira.plugi... ] Jeff MAURY edited comment on JBIDE-24775 at 8/1/17 7:54 AM: ------------------------------------------------------------ [~rob.stryker] have spare minutes to look into this issue that is closely related to JBIDE-27774? was (Author: adietish): [~rob.stryker] have spare minutes to look into this issue that is closely related to JBIDE-27444? > Token field isn't automatically filled in after token extraction > ---------------------------------------------------------------- > > Key: JBIDE-24775 > URL: https://issues.jboss.org/browse/JBIDE-24775 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Dmitrii Bocharov > Fix For: 4.5.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24775) Token field isn't automatically filled in after token extraction

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24775?page=com.atlassian.jira.plugi... ] Jeff MAURY edited comment on JBIDE-24775 at 8/1/17 7:53 AM: ------------------------------------------------------------ [~rob.stryker] have spare minutes to look into this issue that is closely related to JBIDE-27444? was (Author: adietish): [~rob.stryker] have spare minutes to look into this issue that is closely related to JBIDE-2744? > Token field isn't automatically filled in after token extraction > ---------------------------------------------------------------- > > Key: JBIDE-24775 > URL: https://issues.jboss.org/browse/JBIDE-24775 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Dmitrii Bocharov > Fix For: 4.5.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23136) Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23136?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23136: ------------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.Final) > Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag > ----------------------------------------------------------------------------------- > > Key: JBIDE-23136 > URL: https://issues.jboss.org/browse/JBIDE-23136 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Marián Labuda > Assignee: Dmitrii Bocharov > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.5.x > > Attachments: FedoraImageStream.png, ImagesWithDigest.png, eap64-basic-s2i-new-app-from-cli-1.png, eap64-basic-s2i-new-app-from-jbosstools-1.png, local-docker-images-after-pull-1.png > > > I have a docker connection to local docker daemon and a CDK docker connection. I am pushing an image from a docker connection to CDK registry via Deploy Image to OpenShift wizard. Push of an image pass, but it results into an image with no tag, see: > 172.30.192.49:5000/msa/msa <none> 238200ae067d 4 months ago 1.05 GB > Such images are not shown in docker explorer under a docker connection because of upstream bug ERT-411 > Steps to reproduce: > - have a project with a file named {{Dockerfile}} with the following content (1 line): > {code} > FROM fedora:latest > {code} > - Select the file in the project explorer, then {{Run As > Docker Image Build}}. Use the CDK connection and give it a name (eg: {{username/fedora}}) > - Select the image in the Docker Explorer view, then {{Deploy to OpenShift}}. > - In the wizard, select the option to push the image to the registry (add a dummy port if needed) > - once the operation completed, there's an unexpected image named like {{172.30.164.33:5000/<project>/fedora}} in the output of the {{docker images}} command (in CLI) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24501) Deploy Docker Image wizard: NPE when trying to deploy image previously pushed to docker registry

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24501?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24501: ------------------------------------- Labels: deploy_docker_wizard openshift_v3 (was: ) > Deploy Docker Image wizard: NPE when trying to deploy image previously pushed to docker registry > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-24501 > URL: https://issues.jboss.org/browse/JBIDE-24501 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.5.0.Final > > Attachments: image-2017-05-23-12-00-51-733.png, image-2017-05-23-12-07-14-028.png, image-2017-05-23-12-10-06-694.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22969) Make sure OpenShift Tools support proxies

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22969?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22969: ------------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.Final) > Make sure OpenShift Tools support proxies > ----------------------------------------- > > Key: JBIDE-22969 > URL: https://issues.jboss.org/browse/JBIDE-22969 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Reporter: Alexey Kazakov > Assignee: Dmitrii Bocharov > Fix For: 4.5.x > > Attachments: proxy_settings.png, proxy_settings_2.png > > > CDK is now support proxy servers. We also should make sure OpenShift Tools works fine with proxies too. > If devstudio and cdk are installed using DevSuite installer and user configured proxy server correctly then everything should just work on Eclipse side. > This issue covers: > - testing > - creating all needed (currently missing) automated tests (including reddeer/swt bot Integration Tests) > - fixing any problems we have in OpenShift tooling regarding proxy support. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24560) Server adapter very slow to restart in debug

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24560?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-24560: ------------------------------------------ I believe that this issue is resolved with my patch for JBIDE-24184 > Server adapter very slow to restart in debug > --------------------------------------------- > > Key: JBIDE-24560 > URL: https://issues.jboss.org/browse/JBIDE-24560 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Jeff MAURY > Assignee: Rob Stryker > Labels: openshift, openshift_v3, server_adapter > Fix For: 4.5.0.Final > > > When the server adapter has been created and just started, if you restart in debug, it is very slow to restart. It seems to happen only the first time after you created it and started. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2017