July 2019 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26692) Several packages fails to install using yum on RHEL 7.7

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26692?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26692: ------------------------------- Fix Version/s: 4.13.0.AM1 (was: 4.12.0.Final) > Several packages fails to install using yum on RHEL 7.7 > ------------------------------------------------------- > > Key: JBIDE-26692 > URL: https://issues.jboss.org/browse/JBIDE-26692 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Affects Versions: 4.12.0.AM1 > Environment: RHEL 7.7 beta > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Major > Fix For: 4.13.0.AM1 > > Attachments: pulp.repo > > > Several packages fails to install on RHEL 7.7 beta using yum command: > *Content of the {color:red}/etc/yum.repos.d/pulp.repo{color} file after provisioning (or see the pulp.repo file in the attahcment):* > https://pastebin.com/NdBHhvae > *Here is the list of packages that are failing to install (and links to bugzilla):* > redhat-lsb - https://bugzilla.redhat.com/show_bug.cgi?id=1722551 > gcc-c++ - https://bugzilla.redhat.com/show_bug.cgi?id=1723208 > glibc-devel - https://bugzilla.redhat.com/show_bug.cgi?id=1723212 > krb5-devel - https://bugzilla.redhat.com/show_bug.cgi?id=1723213 > libtool - https://bugzilla.redhat.com/show_bug.cgi?id=1723214 > readline-devel - https://bugzilla.redhat.com/show_bug.cgi?id=1723215 > rpm-build - https://bugzilla.redhat.com/show_bug.cgi?id=1723216 > abrt-cli, abrt-addon-ccpp - https://bugzilla.redhat.com/show_bug.cgi?id=1723231 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26676) Central CI: Update mac slaves in Central CI

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26676?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26676: ------------------------------- Fix Version/s: 4.13.0.AM1 (was: 4.12.0.Final) > Central CI: Update mac slaves in Central CI > ------------------------------------------- > > Key: JBIDE-26676 > URL: https://issues.jboss.org/browse/JBIDE-26676 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests > Affects Versions: 4.12.0.Final > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.13.0.AM1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26695) OpenShift ITests: adapt itests for OpenShift 4

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26695?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26695: ------------------------------- Fix Version/s: 4.13.0.AM1 (was: 4.12.0.Final) > OpenShift ITests: adapt itests for OpenShift 4 > ---------------------------------------------- > > Key: JBIDE-26695 > URL: https://issues.jboss.org/browse/JBIDE-26695 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, openshift > Affects Versions: 4.12.0.Final > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.13.0.AM1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18818) Test timeout in org.jboss.tools.jsf.verification.test

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-18818?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-18818: ------------------------------- Fix Version/s: (was: 4.3.x) > Test timeout in org.jboss.tools.jsf.verification.test > ----------------------------------------------------- > > Key: JBIDE-18818 > URL: https://issues.jboss.org/browse/JBIDE-18818 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.2.1.CR1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 4.12.0.Final > > > Tests that time out due to blocking UI or other thread lock result in builds that are recorded as ABORTED [0]. This isn't a problem in terms of publishing new content because the build runs quickly, publishes the new bits, and THEN starts running tests. > [0] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-javaee_4.... > But where it IS a problem is where we use a buildflow job to run the whole stack of JBT projects. Buildflows will also abort if they encounter an aborted job [1]. > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow... > Why is this a problem? Because when we do a weekend spin (or respin) not all the projects in the stack are guaranteed to rebuild to verify all the downstream component tests all still work. > -- > If you cannot fix these tests so they run cleanly in Jenkins, please disable them or move them such that they can still be run LOCALLY using a profile, but will be skipped in Jenkins. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18818) Test timeout in org.jboss.tools.jsf.verification.test

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-18818?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-18818. ------------------------------ Resolution: Done > Test timeout in org.jboss.tools.jsf.verification.test > ----------------------------------------------------- > > Key: JBIDE-18818 > URL: https://issues.jboss.org/browse/JBIDE-18818 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.2.1.CR1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 4.12.0.Final > > > Tests that time out due to blocking UI or other thread lock result in builds that are recorded as ABORTED [0]. This isn't a problem in terms of publishing new content because the build runs quickly, publishes the new bits, and THEN starts running tests. > [0] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-javaee_4.... > But where it IS a problem is where we use a buildflow job to run the whole stack of JBT projects. Buildflows will also abort if they encounter an aborted job [1]. > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow... > Why is this a problem? Because when we do a weekend spin (or respin) not all the projects in the stack are guaranteed to rebuild to verify all the downstream component tests all still work. > -- > If you cannot fix these tests so they run cleanly in Jenkins, please disable them or move them such that they can still be run LOCALLY using a profile, but will be skipped in Jenkins. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26733) 'Launcher Application' link is not present in the Red Hat Central and is also missing in the search (in Red Hat CodeReady Studio)

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26733?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26733: ------------------------------- Fix Version/s: 4.13.0.AM1 > 'Launcher Application' link is not present in the Red Hat Central and is also missing in the search (in Red Hat CodeReady Studio) > --------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26733 > URL: https://issues.jboss.org/browse/JBIDE-26733 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.12.0.AM1 > Environment: OS X 10.14.5 > Reporter: Zbyněk Červinka > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.13.0.AM1 > > Attachments: Red Hat Central.png, Search.png > > > See the "Red Hat Central.png" image in the attachment (the image shows missing "Launcher Application" link). > The "Launcher Application" is also missing from the search (Search.png image in the attachment). -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26688) "jaxws-retail" quickstart from Red Hat Central shows errors after import

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26688?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26688: ------------------------------- Fix Version/s: 4.13.x > "jaxws-retail" quickstart from Red Hat Central shows errors after import > ------------------------------------------------------------------------ > > Key: JBIDE-26688 > URL: https://issues.jboss.org/browse/JBIDE-26688 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.12.0.AM1 > Environment: OS X 10.14.5 > Reporter: Zbyněk Červinka > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.13.x > > > h1. *"jaxws-retail" quickstart from Red Hat Central shows errors after import* > {color:red}*jboss-jaxws-retail-client -> Client.java [unresolvable imports]:*{color} > import org.jboss.quickstarts.ws.jaxws.samples.retail.profile.Customer; > import org.jboss.quickstarts.ws.jaxws.samples.retail.profile.DiscountRequest; > import org.jboss.quickstarts.ws.jaxws.samples.retail.profile.DiscountResponse; > import org.jboss.quickstarts.ws.jaxws.samples.retail.profile.ProfileMgmt; > {color:red}*jboss-jaxws-retail-service -> ProfileMgmtBean.java:*{color} > *DiscountResponse* cannot be resolved to a type > {color:red}*jboss-jaxws-retail-service - > pom.xml:*{color} > Error while running wsconsume. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26687) "ejb-security-interceptors" quickstart from Red Hat Central contains errors after import and the "Show the quick fix dialog" checkbox is enabled

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26687?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26687: ------------------------------- Fix Version/s: 4.13.x > "ejb-security-interceptors" quickstart from Red Hat Central contains errors after import and the "Show the quick fix dialog" checkbox is enabled > ------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-26687 > URL: https://issues.jboss.org/browse/JBIDE-26687 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.12.0.AM1 > Environment: OS X 10.14.5 > Reporter: Zbyněk Červinka > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.13.x > > Attachments: Show the quick fix dialog.png > > > *The "Show the quick fix dialog" checkbox is enabled after import* > - see the "{color:red}Show the quick fix dialog.png{color}" image in the attahcment > *The are errors in the 'Problem view'*: > - cvc-complex-type.2.4.a: Invalid content was found starting with element 'jee:interceptor-binding'. > - Referenced file contains errors (jar:file:/Applications/codereadystudio-19-06-13/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190529-1140.jar!/schema/xsd/jboss-ejb3-spec-2_0.xsd) -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26686) "ejb-remote" quickstart from Red Hat Central contains errors after import and the "Show the quick fix dialog" checkbox is enabled

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26686?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26686: ------------------------------- Fix Version/s: 4.13.x > "ejb-remote" quickstart from Red Hat Central contains errors after import and the "Show the quick fix dialog" checkbox is enabled > --------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26686 > URL: https://issues.jboss.org/browse/JBIDE-26686 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.12.0.AM1 > Environment: OS X 10.14.5 > Reporter: Zbyněk Červinka > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.13.x > > Attachments: Show the quick fix dialog.png, problem_view.png > > > *The "Show the quick fix dialog" checkbox is enabled after import* > - see the "{color:red}Show the quick fix dialog.png{color}" image in the attahcment > *Errors are contained in the following files ( see the {color:red}problem_view.png{color} in the attachment).* > - CounterBean.java > - CalculatorBean.java > - pom.xml > [pom.xml] For artifact {org.jboss.spec.javax.annotation:jboss-annotations-api_1.2_spec:null:jar}: The version cannot be empty. > [pom.xml] Project build error: 'dependencies.dependency.version' for org.jboss.spec.javax.annotation:jboss-annotations-api_1.2_spec:jar is missing. > [pom.xml] Project build error: Non-resolvable import POM: Could not find artifact org.jboss.spec:jboss-javaee-7.0:pom:1.0.3.Final-redhat-2 in central > [CounterBean.java CalculatorBean.java] > The import javax.ejb cannot be resolved -- 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 updated JBIDE-26663: ------------------------------- Fix Version/s: 4.13.x > 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 > Fix For: 4.13.x > > > 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2019