June 2019 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26539) Openshift connection dialog not showing authentication fields

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26539?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26539: ------------------------------- Fix Version/s: 4.12.0.Final (was: 4.12.0.AM1) > Openshift connection dialog not showing authentication fields > ------------------------------------------------------------- > > Key: JBIDE-26539 > URL: https://issues.jboss.org/browse/JBIDE-26539 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.9.0.Final > Reporter: Lionel Orellana > Assignee: André Dietisheim > Priority: Major > Labels: connection_wizard > Fix For: 4.12.0.Final > > Attachments: image-2019-02-11-21-03-11-730.png, screenshot-1.png > > > When I open the New Openshift Connection wizard the Authentication panel is empty. There are not fields to chose auth type or anything at all. > Eclipse 2018-12 (4.10) > !screenshot-1.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 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.12.0.Final (was: 4.12.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.12.0.Final > > 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)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26526) Review and update parameters for as.itests

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26526?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26526: ------------------------------- Fix Version/s: 4.12.0.Final (was: 4.12.0.AM1) > Review and update parameters for as.itests > ------------------------------------------ > > Key: JBIDE-26526 > URL: https://issues.jboss.org/browse/JBIDE-26526 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, server > Affects Versions: 4.11.0.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.12.0.Final > > > Update tests to have something more meaningful than this: > org.jboss.tools.as.itests.server.publishing.DeploymentAssemblyExternalArchiveVarWarTest.testVariableReference[29] (from org.jboss.tools.as.itests.ASToolsIntegrationTestSuite) -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26507) Missing copyright headers in source files

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26507?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26507: ------------------------------- Fix Version/s: 4.12.0.Final (was: 4.12.0.AM1) > Missing copyright headers in source files > ----------------------------------------- > > Key: JBIDE-26507 > URL: https://issues.jboss.org/browse/JBIDE-26507 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.10.0.AM1 > Reporter: Josef Kopriva > Assignee: Koen Aers > Priority: Minor > Fix For: 4.12.0.Final > > > Copyright header is missing in a lot of source files(even in lastly added files). This should be added during refactoring or adding new source files. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26506) Remediation page showing up when installing RHAMT from central - missing org.eclipse.emf.transaction

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26506?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26506: ------------------------------- Fix Version/s: 4.12.0.Final (was: 4.12.0.AM1) > Remediation page showing up when installing RHAMT from central - missing org.eclipse.emf.transaction > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-26506 > URL: https://issues.jboss.org/browse/JBIDE-26506 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, central-update > Affects Versions: 4.11.0.AM1 > Reporter: Ondrej Dockal > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.12.0.Final > > > {code} > Cannot complete the install because one or more required items could not be found. > Software being installed: RHAMT 4.2.0.Final (org.jboss.tools.windup.feature.feature.group 4.2.0.Final) > Missing requirement: Model 4.2.0.Final (org.jboss.tools.windup.model 4.2.0.Final) requires 'osgi.bundle; org.eclipse.emf.transaction 0.0.0' but it could not be found > Cannot satisfy dependency: > From: RHAMT 4.2.0.Final (org.jboss.tools.windup.feature.feature.group 4.2.0.Final) > To: org.eclipse.equinox.p2.iu; org.jboss.tools.windup.model [4.2.0.Final,4.2.0.Final] > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26503) Several Imported Launcher Application projects has some error in their files after importing

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26503?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26503: ------------------------------- Fix Version/s: 4.12.0.Final (was: 4.12.0.AM1) > Several Imported Launcher Application projects has some error in their files after importing > -------------------------------------------------------------------------------------------- > > Key: JBIDE-26503 > URL: https://issues.jboss.org/browse/JBIDE-26503 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.10.0.AM1 > Environment: OS X 10.13.6 > Reporter: Zbyněk Červinka > Priority: Major > Fix For: 4.12.0.Final > > Attachments: cache_vert.x_red hat_1.png, cache_vert.x_red hat_2.png > > > Launcher application projects and their errors (description with settings): > 1) Mission: "crud", Runtime: "thorntail community" > 2) Mission: "crud", Runtime: "thorntail red hat" > - 4 missing HTML </p> tags in file "src/licences/bouncy castle licence - licence.html" on line 50, 51, 52, 53 > 3) Mission: "crud", Runtime: "vert.x community" > 4) Mission: "crud", Runtime: "vert.x red hat" > - 3 errors in the project: > a) Failure to transfer org.codehaus.mojo:buildnumber-maven-plugin:pom:1.4 from https://repository.jboss.org/nexus/content/groups/public-jboss/ was cached in the local repository, resolution will not be... > b) The project was not built since its build path is incomplete. Cannot find the class file for java.lang.Object. Fix the build path then try building this project > c) The type java.lang.Object cannot be resolved. It is indirectly referenced from required .class files > 5) Mission: "cache", Runtime: "vert.x red hat" > 6) Mission: "cache", Runtime: "vert.x community" > - several errors during import and after import (2 images; also in the attachment): > !cache_vert.x_red hat_2.png|thumbnail! !cache_vert.x_red hat_1.png|thumbnail! > Maybe several other errors. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26480) Missing org.eclipse.epp.logging.aeri.ide plugin in devstudio

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26480?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26480: ------------------------------- Fix Version/s: 4.12.0.Final (was: 4.12.0.AM1) > Missing org.eclipse.epp.logging.aeri.ide plugin in devstudio > ------------------------------------------------------------- > > Key: JBIDE-26480 > URL: https://issues.jboss.org/browse/JBIDE-26480 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: target-platform > Affects Versions: 4.10.0.AM1 > Reporter: Ondrej Dockal > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.12.0.Final > > > Moving TP from 4.9 to 4.10 caused missing org.eclipse.epp.logging.aeri.ide plugin. > One case how to reproduce this issue is to install RedDeer 2.4.0.M2 (Maybe even older 2.3.0.Final release) which requires aeri.core and aeri.ide plugins to be available. Restarting of devstudio after instalaltion or RD will shows in error log this: > {code} > Error > Tue Nov 20 10:11:03 CET 2018 > FrameworkEvent ERROR > org.osgi.framework.BundleException: Could not resolve module: org.eclipse.reddeer.eclipse.test [1196] > Unresolved requirement: Require-Bundle: org.eclipse.epp.logging.aeri.ide > -> Bundle-SymbolicName: org.eclipse.epp.logging.aeri.ide; bundle-version="2.0.7.v20180504-0806"; singleton:="true" > org.eclipse.epp.logging.aeri.ide [345] > Unresolved requirement: Import-Package: org.apache.lucene.document; version="[7.1.0,8.0.0)" > {code} > This is suggesting that it has something in common with lucene.core plugin. this might help identifying the root cause. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[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: ------------------------------- Fix Version/s: 4.12.0.Final (was: 4.12.0.AM1) > 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.12.0.Final > > > 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-26652) UMB message specification for devstudio and others products

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26652?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26652: ------------------------------- Fix Version/s: 4.12.0.Final (was: 4.12.0.AM1) > UMB message specification for devstudio and others products > ----------------------------------------------------------- > > Key: JBIDE-26652 > URL: https://issues.jboss.org/browse/JBIDE-26652 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.12.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Major > Labels: jenkins, quality > Fix For: 4.12.0.Final > > > Take care of product build specification for new UMB artifacts definition. > https://pagure.io/fedora-ci/messages/issue/52 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26646) Central ITests: A lot of tests are failing and server is not running

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26646?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26646: ------------------------------- Fix Version/s: 4.12.0.Final (was: 4.12.0.AM1) > Central ITests: A lot of tests are failing and server is not running > -------------------------------------------------------------------- > > Key: JBIDE-26646 > URL: https://issues.jboss.org/browse/JBIDE-26646 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, integration-tests > Affects Versions: 4.12.0.AM1 > Reporter: Josef Kopriva > Assignee: Zbyněk Červinka > Priority: Major > Fix For: 4.12.0.Final > > > There is a quite a lot of failures in job: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > There can be 2 approaches: > * Downgrade used server to EAP 6.4(quickstarts in central are probably for this server) and fix java settings for it > or > * Upgrade server to the latest version, but expect a lot of failures due to old quickstarts. > I prefer the 1st approach. -- 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