June 2019 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4777) Please document procedure (if possible) for defining Debug port, Deployment path

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBDS-4777?page=com.atlassian.jira.plugin.... ] André Dietisheim edited comment on JBDS-4777 at 6/21/19 6:16 AM: ----------------------------------------------------------------- [~mgreenbe] PR https://github.com/jbosstools/jbosstools-openshift/pull/1847 was merged into master, topic branch removed. The improvement that it's addressing is now available in nightly binary builds. If you want to keep using our plugins source, simply switch to master and pull from upstream (https://github.com/jbosstools/jbosstools-openshift/) /master. was (Author: adietish): [~mgreenbe] PR https://github.com/jbosstools/jbosstools-openshift/pull/1847 was merged into master, topic branch removed. The improvement that it's addressing is now available in nightly binary builds. If you want to keep using our plugins source, simply switch to master and pull from upstream (https://github.com/jbosstools/jbosstools-openshift/pull/1847) /master. > Please document procedure (if possible) for defining Debug port, Deployment path > -------------------------------------------------------------------------------- > > Key: JBDS-4777 > URL: https://issues.jboss.org/browse/JBDS-4777 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Feature Request > Components: openshift > Affects Versions: 12.11.0.GA > Environment: CodeReady Studio 12.11 > Reporter: Rick Wagner > Assignee: André Dietisheim > Priority: Major > Labels: openshift > Fix For: 12.x > > Attachments: Dockerfile, Problem_Description.pdf, screenshot-1.png, screenshot-10.png, screenshot-2.png, screenshot-3.png, screenshot-4.png, screenshot-5.png, screenshot-6.png, screenshot-7.png, screenshot-8.png, screenshot-9.png > > > Please document procedure for pre-filling the following in Adapter Server Settings: > - Pod Deployment Path > - Debugging Key > - Debugging Port > Can this be done via image Labels from an imported Docker image? -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26663) Error occured while running bean post processors after import Spring Starter Project

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26663?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-26663: ---------------------------------- Assignee: Jeff MAURY > Error occured while running bean post processors after import Spring Starter Project > ------------------------------------------------------------------------------------ > > Key: JBIDE-26663 > URL: https://issues.jboss.org/browse/JBIDE-26663 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.12.0.AM1 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Priority: Minor > > After import there is an error in error log: > {code:java} > null > org.springframework.ide.eclipse.beans.core > Warning > Mon Jun 10 09:00:00 CEST 2019 > Error occured while running bean post processors > java.lang.IllegalStateException: Error processing condition on org.springframework.boot.autoconfigure.cache.CacheAutoConfiguration > at org.springframework.boot.autoconfigure.condition.SpringBootCondition.matches(SpringBootCondition.java:64) > at org.springframework.context.annotation.ConditionEvaluator.shouldSkip(ConditionEvaluator.java:102) > at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader$TrackedConditionEvaluator.shouldSkip(ConfigurationClassBeanDefinitionReader.java:444) > at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader$TrackedConditionEvaluator.shouldSkip(ConfigurationClassBeanDefinitionReader.java:433) > 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.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) > at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) > at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) > at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.base/java.lang.Thread.run(Thread.java:834) > Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.boot.autoconfigure.condition.BeanTypeRegistry': Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.boot.autoconfigure.condition.BeanTypeRegistry]: No default constructor found; nested exception is java.lang.NoSuchMethodException: org.springframework.boot.autoconfigure.condition.BeanTypeRegistry.<init>() > at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:1159) > at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1103) > at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:511) > at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:481) > at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:312) > at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230) > at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:308) > at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202) > at org.springframework.boot.autoconfigure.condition.BeanTypeRegistry.get(BeanTypeRegistry.java:369) > 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) > ... 19 more > Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.boot.autoconfigure.condition.BeanTypeRegistry]: No default constructor found; nested exception is java.lang.NoSuchMethodException: org.springframework.boot.autoconfigure.condition.BeanTypeRegistry.<init>() > at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:85) > at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:1151) > ... 33 more > Caused by: java.lang.NoSuchMethodException: org.springframework.boot.autoconfigure.condition.BeanTypeRegistry.<init>() > at java.base/java.lang.Class.getConstructor0(Class.java:3350) > at java.base/java.lang.Class.getDeclaredConstructor(Class.java:2554) > at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:80) > ... 34 more > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-738) [API] Add color constants for disabled background and foreground colors [EBZ#548190]

by Friendly Jira Robot (Jira)

Friendly Jira Robot created ERT-738: --------------------------------------- Summary: [API] Add color constants for disabled background and foreground colors [EBZ#548190] Key: ERT-738 URL: https://issues.jboss.org/browse/ERT-738 Project: Eclipse Release Train Issue Type: Task Components: Platform Reporter: Friendly Jira Robot As part of the discussion for bug 4745, it has been decided that SWT would benefit from defining a disabled background and foreground color constant. Platform specific bugs for this work should be filed separately with this ticket as a blocker. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26670) Update 4.12.0.Final Target Platform (Docker tooling, ...) for 2019-06

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26670?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26670: ------------------------------- Attachment: p2diff_log_jbosstools_2019-06-20_15-52.txt > Update 4.12.0.Final Target Platform (Docker tooling, ...) for 2019-06 > --------------------------------------------------------------------- > > Key: JBIDE-26670 > URL: https://issues.jboss.org/browse/JBIDE-26670 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.12.0.AM1 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.12.0.Final > > Attachments: p2diff_log_jbosstools_2019-06-20_15-52.txt > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-736) [GTK] Add color constant for disabled background and foreground colors [EBZ#548191]

by Eric Williams (Jira)

[ https://issues.jboss.org/browse/ERT-736?page=com.atlassian.jira.plugin.sy... ] Eric Williams resolved ERT-736. ------------------------------- Resolution: Done > [GTK] Add color constant for disabled background and foreground colors [EBZ#548191] > ----------------------------------------------------------------------------------- > > Key: ERT-736 > URL: https://issues.jboss.org/browse/ERT-736 > Project: Eclipse Release Train > Issue Type: Task > Components: Platform > Reporter: Friendly Jira Robot > Assignee: Eric Williams > Priority: Major > Labels: SWT, bzira > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-737) [GTK] Clean up system color CSS parsing [EBZ#548286]

by Eric Williams (Jira)

[ https://issues.jboss.org/browse/ERT-737?page=com.atlassian.jira.plugin.sy... ] Eric Williams reassigned ERT-737: --------------------------------- Sprint: devex #168 June 2019 Assignee: Eric Williams > [GTK] Clean up system color CSS parsing [EBZ#548286] > ---------------------------------------------------- > > Key: ERT-737 > URL: https://issues.jboss.org/browse/ERT-737 > Project: Eclipse Release Train > Issue Type: Task > Components: Platform > Reporter: Friendly Jira Robot > Assignee: Eric Williams > Priority: Major > Labels: 4.13_M1, SWT, bzira > > Adopt GtkStyleContext extraction wherever possible, similar to the fixes from bug 546252. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-736) [GTK] Add color constant for disabled background and foreground colors [EBZ#548191]

by Eric Williams (Jira)

[ https://issues.jboss.org/browse/ERT-736?page=com.atlassian.jira.plugin.sy... ] Eric Williams reassigned ERT-736: --------------------------------- Sprint: devex #168 June 2019 Assignee: Eric Williams > [GTK] Add color constant for disabled background and foreground colors [EBZ#548191] > ----------------------------------------------------------------------------------- > > Key: ERT-736 > URL: https://issues.jboss.org/browse/ERT-736 > Project: Eclipse Release Train > Issue Type: Task > Components: Platform > Reporter: Friendly Jira Robot > Assignee: Eric Williams > Priority: Major > Labels: SWT, bzira > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-736) [GTK] Add color constant for disabled background and foreground colors [EBZ#548191]

by Friendly Jira Robot (Jira)

Friendly Jira Robot created ERT-736: --------------------------------------- Summary: [GTK] Add color constant for disabled background and foreground colors [EBZ#548191] Key: ERT-736 URL: https://issues.jboss.org/browse/ERT-736 Project: Eclipse Release Train Issue Type: Task Components: Platform Reporter: Friendly Jira Robot -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-737) [GTK] Clean up system color CSS parsing [EBZ#548286]

by Friendly Jira Robot (Jira)

Friendly Jira Robot created ERT-737: --------------------------------------- Summary: [GTK] Clean up system color CSS parsing [EBZ#548286] Key: ERT-737 URL: https://issues.jboss.org/browse/ERT-737 Project: Eclipse Release Train Issue Type: Task Components: Platform Reporter: Friendly Jira Robot Adopt GtkStyleContext extraction wherever possible, similar to the fixes from bug 546252. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-737) [GTK] Clean up system color CSS parsing [EBZ#548286]

by Friendly Jira Robot (Jira)

[ https://issues.jboss.org/browse/ERT-737?page=com.atlassian.jira.plugin.sy... ] Friendly Jira Robot resolved ERT-737. ------------------------------------- Resolution: Done > [GTK] Clean up system color CSS parsing [EBZ#548286] > ---------------------------------------------------- > > Key: ERT-737 > URL: https://issues.jboss.org/browse/ERT-737 > Project: Eclipse Release Train > Issue Type: Task > Components: Platform > Reporter: Friendly Jira Robot > Priority: Major > Labels: 4.13_M1, SWT, bzira > > Adopt GtkStyleContext extraction wherever possible, similar to the fixes from bug 546252. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 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 June 2019