[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:
-----------------------------
Fix Version/s: 12.14.0.AM1
(was: 12.13.0.GA)
> Central projects Wizard sometimes fails to open
> -----------------------------------------------
>
> Key: JBDS-4735
> URL: https://issues.jboss.org/browse/JBDS-4735
> Project: Red Hat CodeReady 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.14.0.AM1
>
> Attachments: central.tar.gz, image-2018-10-17-09-24-31-555.png, screenshot-1.png
>
>
> There is "openInIDE" used in 3 places in "main.min.js" in central source code*. When the central reloads and works normally, "openInIDE" is a function (probably defined in Java code or somewhere out of the "main.min.js" file) with following implementation:
> function openInIDE() {
> var result = callJava(1, '9aee3b4a3f3b40ed26f47d66375b25e3', Array.prototype.slice.call(arguments));
> if (typeof result == 'string' && result.indexOf('org.eclipse.swt.browser.error') == 0) {
> var error = new Error(result.substring(29));
> throw error;
> }
> return result;
> }
> After the issue appears, "typedef openInIDE" is undefined, which causes probably the issues.
> *Additional information to the 3 places, where "openInIDE" appears - it appears in 2 functions:
> - registerButtonClicks() - here is the "openInIDE" needed for loading and displaying the central correctly
> - delegateToIDE(a, b) - here is the "openInIDE" needed for opening the wizard to the quickstart
> OLDER DESCRIPTION (does not describes the issue enough, but I decided to keep it for more details about the issue):
> ----------------------------------------------------------------------------------------------------------------------
> 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
> Addition info:
> Considering that central itests fails for this sometimes fresh installation without restart may cause this. Although it happen again after running devstudio for some time and restarting Central view.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[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.14.0.AM1
(was: 4.13.0.Final)
> 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.14.0.AM1
>
> 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.13.8#713008)
6 years, 5 months
[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.14.0.AM1
(was: 4.13.0.Final)
> 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.14.0.AM1
>
>
> 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.13.8#713008)
6 years, 5 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:
-------------------------------
Fix Version/s: 4.14.0.AM1
(was: 4.13.0.Final)
> 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.14.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.13.8#713008)
6 years, 5 months
[JBoss JIRA] (JBIDE-26475) Update lucene version in target platform
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26475?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26475:
-------------------------------
Fix Version/s: 4.14.0.AM1
(was: 4.13.0.Final)
> Update lucene version in target platform
> ----------------------------------------
>
> Key: JBIDE-26475
> URL: https://issues.jboss.org/browse/JBIDE-26475
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build, target-platform
> Affects Versions: 4.10.0.AM1
> Reporter: Josef Kopriva
> Priority: Major
> Fix For: 4.14.0.AM1
>
>
> Investigate and identify why do we multiple version of org.apache.lucene.8 packages in target plaform(e.g. in eclipse TP is version 7.5, but in target platform is 7.1).
> It would be also nice, if comments would be added in target file to know why we have different versions.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (JBIDE-26463) Create Eclipse Marketplace entry for Dependency Analytics (fabric8 plugin)
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26463?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26463:
-------------------------------
Fix Version/s: 4.14.0.AM1
(was: 4.13.0.Final)
> Create Eclipse Marketplace entry for Dependency Analytics (fabric8 plugin)
> --------------------------------------------------------------------------
>
> Key: JBIDE-26463
> URL: https://issues.jboss.org/browse/JBIDE-26463
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: marketplace, updatesite
> Affects Versions: 4.10.0.AM1
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Major
> Fix For: 4.14.0.AM1
>
>
> Per discussion w/ [~mickael_istria] [~rpdavis] and [~jeffmaury], we should create a new Eclipse Marketplace entry for the fabric8 analytics plugin.
> This will require that the plugin & feature have its own dedicated update site, unless we plan to just point the entry at the latest devstudio or jbosstools site.
> Will also need to determine how to describe the plugin, provide an icon and/or screenshot, etc.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months