[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 (was: devex #159 December 2018)
> Central projects Wizard sometimes fails to open
> -----------------------------------------------
>
> Key: JBDS-4735
> URL: https://issues.jboss.org/browse/JBDS-4735
> Project: Red Hat JBoss Developer 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.x
>
> Attachments: central.tar.gz, image-2018-10-17-09-24-31-555.png, screenshot-1.png
>
>
> 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
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-26117) Connection Wizard: Parse Login command (that was copied to clipboard by the web-ui)
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26117?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26117:
-------------------------------
Sprint: devex #159 December 2018, devex #161 January 2019 (was: devex #159 December 2018)
> Connection Wizard: Parse Login command (that was copied to clipboard by the web-ui)
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-26117
> URL: https://issues.jboss.org/browse/JBIDE-26117
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.6.0.Final
> Reporter: Josef Kopriva
> Assignee: Josef Kopriva
> Priority: Major
> Labels: connection_wizard
> Fix For: 4.11.0.AM1
>
>
> The OpenShift web-ui provides a menu entry that creates the oc login command in your local clipboard: https://stackoverflow.com/questions/49548380/cannot-find-openshift-3-logi...
> Currently, Eclipse users would have to paste it to some notepad and use the info in it to manually create a connection. The tooling could facilitate this by parsing the clipboard and creating a connection:
> The Eclipse
> There could be a button for parsing login command in clipboard.
> Steps:
> 1. User logins in web browser in OpenShift Console.
> 2. User clicks on "Copy Login Command"
> 3. In OpenShift tooling there could be button for parse login command from clipboard.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-26452) Explore existing proxy server set up solutions outside RH - proxy requirements definition
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26452?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26452:
-------------------------------
Sprint: devex #157 November 2019, devex #159 December 2018, devex #161 January 2019 (was: devex #157 November 2019, devex #159 December 2018)
> Explore existing proxy server set up solutions outside RH - proxy requirements definition
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-26452
> URL: https://issues.jboss.org/browse/JBIDE-26452
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests, qa
> Affects Versions: 4.10.0.AM1
> Environment: Linux
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Major
> Labels: quality
> Fix For: 4.11.0.AM1
>
>
> Explore existing solutions for proxy configuration that could be done at one step without requiring deep user knowledge.
> Existing docker images with squid (other?) proxy. Licensing, usage within RH intranet. Is there an open source code?
> Requirements for proxy solution:
> * Supports HTTP and HTTPS protocols
> * Clear and configurable logging and other tools
> * runs on linux
> * Open Source solution
> * License usable "in house" (can be use for profit = in enterprise environment)
> * Project is alive/maintained - or we would must maintain our own fork?
> * Community
> * Code on github - preferably
> * uses issue tracking system
> Requirements for putting proxy into action:
> * easy to deploy solution
> * does not require user knowledge of proxy configuration - minimalist config
> * can be updated at place
> * RH certificate can be used
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-26453) Adapters/vscode-openshift tooling onboarding
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26453?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26453:
-------------------------------
Sprint: devex #157 November 2019, devex #159 December 2018, devex #161 January 2019 (was: devex #157 November 2019, devex #159 December 2018)
> Adapters/vscode-openshift tooling onboarding
> --------------------------------------------
>
> Key: JBIDE-26453
> URL: https://issues.jboss.org/browse/JBIDE-26453
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests, qa
> Affects Versions: 4.10.0.AM1
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Critical
> Labels: integration-test, quality
> Fix For: 4.11.0.AM1
>
>
> Jump in adapters stuff:
> * go through repos, get familiar with plugins
> * start exploring locally, build it, run it
> * pick up github issues and start implementing in typescript/java
> * increase unit tests coverage
> * get familiar with infrastructure
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-26478) Errors during import Spring Starter Project
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26478?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26478:
-------------------------------
Component/s: central
(was: build)
> Errors during import Spring Starter Project
> -------------------------------------------
>
> Key: JBIDE-26478
> URL: https://issues.jboss.org/browse/JBIDE-26478
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.10.0.AM1
> Environment: F29
> Reporter: Josef Kopriva
> Assignee: Jeff MAURY
> Priority: Minor
> Fix For: 4.11.0.AM1
>
>
> During import of Spring Starter project there are some errors in error log;
> {code:java}
> eclipse.buildId=12.10.0.AM1-v20181129-0845-B3670
> 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 com.jboss.devstudio.core.product
> Command-line arguments: -data file:/home/jkopriva/devstudio_B3670_2/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.springframework.ide.eclipse.beans.core
> Error
> Fri Nov 30 10:37:18 CET 2018
> Problems occurred when invoking code from plug-in: "org.springframework.ide.eclipse.beans.core".
> java.lang.NoSuchMethodError: org.springframework.beans.factory.support.BeanDefinitionBuilder.genericBeanDefinition(Ljava/lang/Class;Ljava/util/function/Supplier;)Lorg/springframework/beans/factory/support/BeanDefinitionBuilder;
> at org.springframework.boot.autoconfigure.condition.BeanTypeRegistry.get(BeanTypeRegistry.java:363)
> at org.springframework.boot.autoconfigure.condition.OnBeanCondition.collectBeanNamesForType(OnBeanCondition.java:297)
> at org.springframework.boot.autoconfigure.condition.OnBeanCondition.getBeanNamesForType(OnBeanCondition.java:289)
> at org.springframework.boot.autoconfigure.condition.OnBeanCondition.getBeanNamesForType(OnBeanCondition.java:278)
> at org.springframework.boot.autoconfigure.condition.OnBeanCondition.getMatchingBeans(OnBeanCondition.java:189)
> at org.springframework.boot.autoconfigure.condition.OnBeanCondition.getMatchOutcome(OnBeanCondition.java:125)
> at org.springframework.boot.autoconfigure.condition.SpringBootCondition.matches(SpringBootCondition.java:47)
> at org.springframework.context.annotation.ConditionEvaluator.shouldSkip(ConditionEvaluator.java:102)
> at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader$TrackedConditionEvaluator.shouldSkip(ConfigurationClassBeanDefinitionReader.java:443)
> at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader$TrackedConditionEvaluator.shouldSkip(ConfigurationClassBeanDefinitionReader.java:432)
> at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader.loadBeanDefinitionsForConfigurationClass(ConfigurationClassBeanDefinitionReader.java:127)
> at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader.loadBeanDefinitions(ConfigurationClassBeanDefinitionReader.java:116)
> at org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:320)
> at org.springframework.ide.eclipse.metadata.process.JdtConfigurationClassPostProcessor.postProcess(JdtConfigurationClassPostProcessor.java:88)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig$3.run(BeansJavaConfig.java:332)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig.executePostProcessor(BeansJavaConfig.java:321)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig.access$5(BeansJavaConfig.java:319)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig$2.call(BeansJavaConfig.java:233)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig$2.call(BeansJavaConfig.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> {code:java}
> eclipse.buildId=12.10.0.AM1-v20181129-0845-B3670
> 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 com.jboss.devstudio.core.product
> Command-line arguments: -data file:/home/jkopriva/devstudio_B3670_2/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.springframework.ide.eclipse.beans.core
> Warning
> Fri Nov 30 10:37:18 CET 2018
> Error occured while running bean post processors
> java.lang.NoSuchMethodError: org.springframework.beans.factory.support.BeanDefinitionBuilder.genericBeanDefinition(Ljava/lang/Class;Ljava/util/function/Supplier;)Lorg/springframework/beans/factory/support/BeanDefinitionBuilder;
> at org.springframework.boot.autoconfigure.condition.BeanTypeRegistry.get(BeanTypeRegistry.java:363)
> at org.springframework.boot.autoconfigure.condition.OnBeanCondition.collectBeanNamesForType(OnBeanCondition.java:297)
> at org.springframework.boot.autoconfigure.condition.OnBeanCondition.getBeanNamesForType(OnBeanCondition.java:289)
> at org.springframework.boot.autoconfigure.condition.OnBeanCondition.getBeanNamesForType(OnBeanCondition.java:278)
> at org.springframework.boot.autoconfigure.condition.OnBeanCondition.getMatchingBeans(OnBeanCondition.java:189)
> at org.springframework.boot.autoconfigure.condition.OnBeanCondition.getMatchOutcome(OnBeanCondition.java:125)
> at org.springframework.boot.autoconfigure.condition.SpringBootCondition.matches(SpringBootCondition.java:47)
> at org.springframework.context.annotation.ConditionEvaluator.shouldSkip(ConditionEvaluator.java:102)
> at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader$TrackedConditionEvaluator.shouldSkip(ConfigurationClassBeanDefinitionReader.java:443)
> at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader$TrackedConditionEvaluator.shouldSkip(ConfigurationClassBeanDefinitionReader.java:432)
> at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader.loadBeanDefinitionsForConfigurationClass(ConfigurationClassBeanDefinitionReader.java:127)
> at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader.loadBeanDefinitions(ConfigurationClassBeanDefinitionReader.java:116)
> at org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:320)
> at org.springframework.ide.eclipse.metadata.process.JdtConfigurationClassPostProcessor.postProcess(JdtConfigurationClassPostProcessor.java:88)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig$3.run(BeansJavaConfig.java:332)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig.executePostProcessor(BeansJavaConfig.java:321)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig.access$5(BeansJavaConfig.java:319)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig$2.call(BeansJavaConfig.java:233)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig$2.call(BeansJavaConfig.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months