[JBoss JIRA] (JBIDE-26913) cdi.itests for CDI 1.0 and 1.1 contains tests for trim and several failing tests (Asserts and NPEs)
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-26913?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka updated JBIDE-26913:
------------------------------------
Description:
There are several issues in the CDI 1.0 and the CDI 1.1 itests, several actions needs to be performed:
- remove the TRIM tests from the CDI 1.0 and the CDI 1.1 itests
- fix the failing 'testExcludedBeans' WeldExcludeTestCDI10 and WeldExcludeTestCDI11 tests (CDI 1.0 and CDI 1.1)
- fix the failing 'testVetoedAnnotation' VetoedAnnotationTestCDI11 test (CDI 1.1)
- fix the failing 'testParametersAnnotationvalidation' BeanParametersAnnotationTestCDI11 test (CDI 1.1)
- fix the failing 'testExcludedBeans' ExcludeBeanTestCDI11 test (CDI 1.1)
was:
There are several issues in the CDI 1.0 and the CDI 1.1 itests, several actions needs to be performed:
- remove the TRIM tests from the CDI 1.0 and the CDI 1.1 itests
- fix the failing 'testExcludedBeans' WeldExcludeTest test for CDI 1.0 and CDI 1.1 (asserts and NPEs)
- VetoedAnnotationTest -> testVetoedAnnotation is failing for CDI 1.1
- BeanParametersAnnotationTest in org.jboss.tools.cdi.bot.test.beansxml.annotation.cdi11 is failing
- ExcludeBeanTestCDI11 -> testExcludedBeans is failing
> cdi.itests for CDI 1.0 and 1.1 contains tests for trim and several failing tests (Asserts and NPEs)
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26913
> URL: https://issues.jboss.org/browse/JBIDE-26913
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: integration-tests
> Affects Versions: 4.13.0.AM1
> Environment: all OSes
> Reporter: Zbyněk Červinka
> Assignee: Zbyněk Červinka
> Priority: Major
>
> There are several issues in the CDI 1.0 and the CDI 1.1 itests, several actions needs to be performed:
> - remove the TRIM tests from the CDI 1.0 and the CDI 1.1 itests
> - fix the failing 'testExcludedBeans' WeldExcludeTestCDI10 and WeldExcludeTestCDI11 tests (CDI 1.0 and CDI 1.1)
> - fix the failing 'testVetoedAnnotation' VetoedAnnotationTestCDI11 test (CDI 1.1)
> - fix the failing 'testParametersAnnotationvalidation' BeanParametersAnnotationTestCDI11 test (CDI 1.1)
> - fix the failing 'testExcludedBeans' ExcludeBeanTestCDI11 test (CDI 1.1)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (JBIDE-26913) cdi.itests for CDI 1.0 and 1.1 contains tests for trim and several failing tests (Asserts and NPEs)
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-26913?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka updated JBIDE-26913:
------------------------------------
Description:
There are several issues in the CDI 1.0 and the CDI 1.1 itests, several actions needs to be performed:
- remove the TRIM tests from the CDI 1.0 and the CDI 1.1 itests
- fix the failing 'testExcludedBeans' WeldExcludeTestCDI10 and WeldExcludeTestCDI11 tests (CDI 1.0 and CDI 1.1)
- fix the failing 'testVetoedAnnotation' VetoedAnnotationTestCDI11 test (CDI 1.1)
- fix the failing 'testParametersAnnotationvalidation' BeanParametersAnnotationTestCDI11 test (CDI 1.1)
- fix the failing 'testExcludedBeans' ExcludeBeanTestCDI11 test (CDI 1.1)
many many others ... to be defined very soon
was:
There are several issues in the CDI 1.0 and the CDI 1.1 itests, several actions needs to be performed:
- remove the TRIM tests from the CDI 1.0 and the CDI 1.1 itests
- fix the failing 'testExcludedBeans' WeldExcludeTestCDI10 and WeldExcludeTestCDI11 tests (CDI 1.0 and CDI 1.1)
- fix the failing 'testVetoedAnnotation' VetoedAnnotationTestCDI11 test (CDI 1.1)
- fix the failing 'testParametersAnnotationvalidation' BeanParametersAnnotationTestCDI11 test (CDI 1.1)
- fix the failing 'testExcludedBeans' ExcludeBeanTestCDI11 test (CDI 1.1)
> cdi.itests for CDI 1.0 and 1.1 contains tests for trim and several failing tests (Asserts and NPEs)
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26913
> URL: https://issues.jboss.org/browse/JBIDE-26913
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: integration-tests
> Affects Versions: 4.13.0.AM1
> Environment: all OSes
> Reporter: Zbyněk Červinka
> Assignee: Zbyněk Červinka
> Priority: Major
>
> There are several issues in the CDI 1.0 and the CDI 1.1 itests, several actions needs to be performed:
> - remove the TRIM tests from the CDI 1.0 and the CDI 1.1 itests
> - fix the failing 'testExcludedBeans' WeldExcludeTestCDI10 and WeldExcludeTestCDI11 tests (CDI 1.0 and CDI 1.1)
> - fix the failing 'testVetoedAnnotation' VetoedAnnotationTestCDI11 test (CDI 1.1)
> - fix the failing 'testParametersAnnotationvalidation' BeanParametersAnnotationTestCDI11 test (CDI 1.1)
> - fix the failing 'testExcludedBeans' ExcludeBeanTestCDI11 test (CDI 1.1)
> many many others ... to be defined very soon
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (JBIDE-26913) cdi.itests for CDI 1.0 and 1.1 contains tests for trim and several failing tests (Asserts and NPEs)
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-26913?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka updated JBIDE-26913:
------------------------------------
Description:
There are several issues in the CDI 1.0 and the CDI 1.1 itests, several actions needs to be performed:
- remove the TRIM tests from the CDI 1.0 and the CDI 1.1 itests
- fix the failing 'testExcludedBeans' WeldExcludeTest test for CDI 1.0 and CDI 1.1 (asserts and NPEs)
- VetoedAnnotationTest -> testVetoedAnnotation is failing for CDI 1.1
- BeanParametersAnnotationTest in org.jboss.tools.cdi.bot.test.beansxml.annotation.cdi11 is failing
- ExcludeBeanTestCDI11 -> testExcludedBeans is failing
was:
There are several issues in the CDI 1.0 and the CDI 1.1 itests, several actions needs to be performed:
- remove the TRIM tests from the CDI 1.0 and the CDI 1.1 itests
- fix the failing 'testExcludedBeans' WeldExcludeTest test for CDI 1.0 and CDI 1.1 (asserts and NPEs)
- VetoedAnnotationTest -> testVetoedAnnotation is failing for CDI 1.1
- BeanParametersAnnotationTest in org.jboss.tools.cdi.bot.test.beansxml.annotation.cdi11 is failing
> cdi.itests for CDI 1.0 and 1.1 contains tests for trim and several failing tests (Asserts and NPEs)
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26913
> URL: https://issues.jboss.org/browse/JBIDE-26913
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: integration-tests
> Affects Versions: 4.13.0.AM1
> Environment: all OSes
> Reporter: Zbyněk Červinka
> Assignee: Zbyněk Červinka
> Priority: Major
>
> There are several issues in the CDI 1.0 and the CDI 1.1 itests, several actions needs to be performed:
> - remove the TRIM tests from the CDI 1.0 and the CDI 1.1 itests
> - fix the failing 'testExcludedBeans' WeldExcludeTest test for CDI 1.0 and CDI 1.1 (asserts and NPEs)
> - VetoedAnnotationTest -> testVetoedAnnotation is failing for CDI 1.1
> - BeanParametersAnnotationTest in org.jboss.tools.cdi.bot.test.beansxml.annotation.cdi11 is failing
> - ExcludeBeanTestCDI11 -> testExcludedBeans is failing
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (JBIDE-26913) cdi.itests for CDI 1.0 and 1.1 contains tests for trim and several failing tests (Asserts and NPEs)
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-26913?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka updated JBIDE-26913:
------------------------------------
Description:
There are several issues in the CDI 1.0 and the CDI 1.1 itests, several actions needs to be performed:
- remove the TRIM tests from the CDI 1.0 and the CDI 1.1 itests
- fix the failing 'testExcludedBeans' WeldExcludeTest test for CDI 1.0 and CDI 1.1 (asserts and NPEs)
- VetoedAnnotationTest -> testVetoedAnnotation is failing for CDI 1.1
- BeanParametersAnnotationTest in org.jboss.tools.cdi.bot.test.beansxml.annotation.cdi11 is failing
was:
There are several issues in the CDI 1.0 and the CDI 1.1 itests, several actions needs to be performed:
- remove the TRIM tests from the CDI 1.0 and the CDI 1.1 itests
- fix the failing 'testExcludedBeans' WeldExcludeTest test for CDI 1.0 and CDI 1.1 (asserts and NPEs)
- VetoedAnnotationTest -> testVetoedAnnotation is failing for CDI 1.1
> cdi.itests for CDI 1.0 and 1.1 contains tests for trim and several failing tests (Asserts and NPEs)
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26913
> URL: https://issues.jboss.org/browse/JBIDE-26913
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: integration-tests
> Affects Versions: 4.13.0.AM1
> Environment: all OSes
> Reporter: Zbyněk Červinka
> Assignee: Zbyněk Červinka
> Priority: Major
>
> There are several issues in the CDI 1.0 and the CDI 1.1 itests, several actions needs to be performed:
> - remove the TRIM tests from the CDI 1.0 and the CDI 1.1 itests
> - fix the failing 'testExcludedBeans' WeldExcludeTest test for CDI 1.0 and CDI 1.1 (asserts and NPEs)
> - VetoedAnnotationTest -> testVetoedAnnotation is failing for CDI 1.1
> - BeanParametersAnnotationTest in org.jboss.tools.cdi.bot.test.beansxml.annotation.cdi11 is failing
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (JBIDE-26913) cdi.itests for CDI 1.0 and 1.1 contains tests for trim and several failing tests (Asserts and NPEs)
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-26913?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka updated JBIDE-26913:
------------------------------------
Description:
There are several issues in the CDI 1.0 and the CDI 1.1 itests, several actions needs to be performed:
- remove the TRIM tests from the CDI 1.0 and the CDI 1.1 itests
- fix the failing 'testExcludedBeans' WeldExcludeTest test for CDI 1.0 and CDI 1.1 (asserts and NPEs)
- VetoedAnnotationTest -> testVetoedAnnotation is failing for CDI 1.1
was:
There are several issues in the CDI 1.0 and the CDI 1.1 itests, several actions needs to be performed:
- remove the TRIM tests from the CDI 1.0 and the CDI 1.1 itests
- fix the failing 'testExcludedBeans' WeldExcludeTest test for CDI 1.0 and CDI 1.1 (asserts and NPEs)
> cdi.itests for CDI 1.0 and 1.1 contains tests for trim and several failing tests (Asserts and NPEs)
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26913
> URL: https://issues.jboss.org/browse/JBIDE-26913
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: integration-tests
> Affects Versions: 4.13.0.AM1
> Environment: all OSes
> Reporter: Zbyněk Červinka
> Assignee: Zbyněk Červinka
> Priority: Major
>
> There are several issues in the CDI 1.0 and the CDI 1.1 itests, several actions needs to be performed:
> - remove the TRIM tests from the CDI 1.0 and the CDI 1.1 itests
> - fix the failing 'testExcludedBeans' WeldExcludeTest test for CDI 1.0 and CDI 1.1 (asserts and NPEs)
> - VetoedAnnotationTest -> testVetoedAnnotation is failing for CDI 1.1
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (JBIDE-26913) cdi.itests for CDI 1.0 and 1.1 contains tests for trim and several failing tests (Asserts and NPEs)
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-26913?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka updated JBIDE-26913:
------------------------------------
Description:
There are several issues in the CDI 1.0 and the CDI 1.1 itests, several actions needs to be performed:
- remove the TRIM tests from the CDI 1.0 and the CDI 1.1 itests
- fix the failing 'testExcludedBeans' WeldExcludeTest test for CDI 1.0 and CDI 1.1 (asserts and NPEs)
> cdi.itests for CDI 1.0 and 1.1 contains tests for trim and several failing tests (Asserts and NPEs)
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26913
> URL: https://issues.jboss.org/browse/JBIDE-26913
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: integration-tests
> Affects Versions: 4.13.0.AM1
> Environment: all OSes
> Reporter: Zbyněk Červinka
> Assignee: Zbyněk Červinka
> Priority: Major
>
> There are several issues in the CDI 1.0 and the CDI 1.1 itests, several actions needs to be performed:
> - remove the TRIM tests from the CDI 1.0 and the CDI 1.1 itests
> - fix the failing 'testExcludedBeans' WeldExcludeTest test for CDI 1.0 and CDI 1.1 (asserts and NPEs)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (JBDS-4805) Error With Reccommenders: java.lang.NoClassDefFoundError: javax/annotation/PostConstruct at org.eclipse.recommenders.internal.rcp.RcpModule$Listener$1.afterInjection(RcpModule.java:278)
by David Guthrie (Jira)
[ https://issues.jboss.org/browse/JBDS-4805?page=com.atlassian.jira.plugin.... ]
David Guthrie updated JBDS-4805:
--------------------------------
> Error With Reccommenders: java.lang.NoClassDefFoundError: javax/annotation/PostConstruct at org.eclipse.recommenders.internal.rcp.RcpModule$Listener$1.afterInjection(RcpModule.java:278)
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4805
> URL: https://issues.jboss.org/browse/JBDS-4805
> Project: Red Hat CodeReady Studio (devstudio)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 12.12.0.GA
> Environment: * eclipse.buildId=12.12.0.GA-v20190628-0434-B4598
> java.version=11.0.3-redhat
> java.vendor=Oracle Corporation
> BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
> Framework arguments: -application org.eclipse.ui.ide.workbench -product com.jboss.devstudio.core.product
> Command-line arguments: -os win32 -ws win32 -arch x86_64 -application org.eclipse.ui.ide.workbench -product com.jboss.devstudio.core.product
> * Camel Fuse development
> Reporter: David Guthrie
> Assignee: Stephane Bouchet
> Priority: Major
> Fix For: 12.x
>
>
> Customer:
> {quote}
> I did an upgrade on Code Ready Studio to 12.12
> and when I go from
> {code}
> public void configure() throws Exception {
> from("file:E:/inputFolder")
> .split().tokenize("\n")
> .to("jms:queue:javininusex");
> }
> {code}
> to
> {code}
> @Override
> public void configure() throws Exception {
> from("{{route.start}}")
> .split().tokenize("\n")
> .log("{{route.start}}")
> .to("{{route.end}}");
> }
> {code}
> it starts show an error on the {{xxxx}} lines. which then sometimes goes to a pop up window that says check the recommender faq at .... (now this won't pop up and I didn't get the address) that is an invalid page.
> {quote}
> Log error
> org.eclipse.recommenders.completion.rcp
> Error
> Fri Oct 18 13:53:29 PDT 2019
> Session processor ‘class org.eclipse.recommenders.internal.calls.rcp.CallCompletionSessionProcessor’ failed with exception.
> {code}
> java.lang.NoClassDefFoundError: javax/annotation/PostConstruct
> at org.eclipse.recommenders.internal.rcp.RcpModule$Listener$1.afterInjection(RcpModule.java:278)
> at com.google.inject.internal.MembersInjectorImpl.notifyListeners(MembersInjectorImpl.java:97)
> at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:95)
> at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254)
> at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
> at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031)
> at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
> at com.google.inject.Scopes$1$1.get(Scopes.java:65)
> at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:40)
> at com.google.inject.internal.FactoryProxy.get(FactoryProxy.java:54)
> at com.google.inject.internal.SingleParameterInjector.inject(SingleParameterInjector.java:38)
> at com.google.inject.internal.SingleParameterInjector.getAll(SingleParameterInjector.java:62)
> at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:84)
> at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254)
> at com.google.inject.internal.FactoryProxy.get(FactoryProxy.java:54)
> at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
> at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031)
> at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
> at com.google.inject.Scopes$1$1.get(Scopes.java:65)
> at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:40)
> at com.google.inject.internal.InjectorImpl$4$1.call(InjectorImpl.java:978)
> at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1024)
> at com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:974)
> at org.eclipse.recommenders.internal.calls.rcp.CallCompletionSessionProcessor.findReceiverTypeAndModel(CallCompletionSessionProcessor.java:136)
> at org.eclipse.recommenders.internal.calls.rcp.CallCompletionSessionProcessor.startSession(CallCompletionSessionProcessor.java:111)
> at org.eclipse.recommenders.completion.rcp.processable.IntelligentCompletionProposalComputer.fireStartSession(IntelligentCompletionProposalComputer.java:305)
> at org.eclipse.recommenders.completion.rcp.processable.IntelligentCompletionProposalComputer.computeCompletionProposals(IntelligentCompletionProposalComputer.java:171)
> at org.eclipse.jdt.internal.ui.text.java.CompletionProposalComputerDescriptor.computeCompletionProposals(CompletionProposalComputerDescriptor.java:336)
> at org.eclipse.jdt.internal.ui.text.java.CompletionProposalCategory.computeCompletionProposals(CompletionProposalCategory.java:340)
> at org.eclipse.jdt.internal.ui.text.java.ContentAssistProcessor.collectProposals(ContentAssistProcessor.java:334)
> at org.eclipse.jdt.internal.ui.text.java.ContentAssistProcessor.computeCompletionProposals(ContentAssistProcessor.java:291)
> at org.eclipse.jface.text.contentassist.ContentAssistant$2.lambda$0(ContentAssistant.java:2014)
> at java.base/java.util.Collections$SingletonSet.forEach(Collections.java:4795)
> at org.eclipse.jface.text.contentassist.ContentAssistant$2.run(ContentAssistant.java:2013)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
> at org.eclipse.jface.text.contentassist.ContentAssistant.computeCompletionProposals(ContentAssistant.java:2010)
> at org.eclipse.jface.text.contentassist.CompletionProposalPopup.computeProposals(CompletionProposalPopup.java:575)
> at org.eclipse.jface.text.contentassist.CompletionProposalPopup.lambda$0(CompletionProposalPopup.java:505)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:72)
> at org.eclipse.jface.text.contentassist.CompletionProposalPopup.showProposals(CompletionProposalPopup.java:500)
> at org.eclipse.jface.text.contentassist.ContentAssistant$AutoAssistListener.lambda$0(ContentAssistant.java:380)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:40)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:185)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3919)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3550)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1173)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1062)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:155)
> at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:635)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:559)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:155)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:660)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:597)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1468)
> {code}
> This seems to be related to upstream issues https://bugs.eclipse.org/bugs/show_bug.cgi?id=541266 and https://bugs.eclipse.org/bugs/show_bug.cgi?id=542689 where recommenders doesn't work with Java 11 and has been removed by upstream eclipse and by the Red Hat Eclipse RPM packages https://issues.jboss.org/browse/RHECLIPSE-82.
> I don't see a way to disable recommenders in codeready studio.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years