[JBoss JIRA] (JBIDE-26708) WildFly quickstart 'messaging-clustering-singleton' shows errors after import
by Zbyněk Červinka (Jira)
[ https://issues.redhat.com/browse/JBIDE-26708?page=com.atlassian.jira.plug... ]
Zbyněk Červinka closed JBIDE-26708.
-----------------------------------
Issue has been fixed, I am closing this jira.
> WildFly quickstart 'messaging-clustering-singleton' shows errors after import
> -----------------------------------------------------------------------------
>
> Key: JBIDE-26708
> URL: https://issues.redhat.com/browse/JBIDE-26708
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.12.0.AM1
> Environment: OS X 10.14.5
> Reporter: Zbyněk Červinka
> Priority: Major
> Fix For: 4.15.0.AM1
>
> Attachments: Problems view.png, Project explorer.png, jboss-ejb3.xml file.png
>
>
> h1. WF quickstart 'messaging-clustering-singleton' shows 3 errors in the jboss-ejb3.xml file after import:
> * Referenced file contains errors (jar:file:/Applications/codereadystudio-j8-wf/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb-delivery-active_1_1.xsd). For more information, right click on the message in the Problems View and select "Show Details..."
> * Referenced file contains errors (jar:file:/Applications/codereadystudio-j8-wf/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb3-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..."
> * Referenced file contains errors (jar:file:/Applications/codereadystudio-j8-wf/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb3-spec-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..."
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (JBIDE-26712) WildFly quickstart 'jts' contains errors after import into Red Hat CodeReady Studio in the 'jboss-ejb3.xml' file
by Zbyněk Červinka (Jira)
[ https://issues.redhat.com/browse/JBIDE-26712?page=com.atlassian.jira.plug... ]
Zbyněk Červinka closed JBIDE-26712.
-----------------------------------
Issue has been fixed, I am closing this jira.
> WildFly quickstart 'jts' contains errors after import into Red Hat CodeReady Studio in the 'jboss-ejb3.xml' file
> ----------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26712
> URL: https://issues.redhat.com/browse/JBIDE-26712
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.12.0.AM1
> Environment: OS X 10.14.5
> Reporter: Zbyněk Červinka
> Priority: Major
> Fix For: 4.15.0.AM1
>
> Attachments: Problems view.png, Project Explorer.png
>
>
> h1. *The "jboss-ejb3.xml" file in the WildFly "jts" quickstart contains the following 2 errors:*
> * cvc-complex-type.2.4.a: Invalid content was found starting with element 'iiop:binding-name'. One of '{"urn:iiop":ejb-name}' is expected.
> * Referenced file contains errors (jar:file:/Applications/codereadystudio-j8-WF-new/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb3-spec-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..."
> h2. Red Hat CodeReady Studio version: 12.12.0.GA
> h2. WildFly version: 17.0.0.Final
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (JBIDE-27135) Fix the failing HTML5Parameterized central.itests testclass on OS X
by Zbyněk Červinka (Jira)
[ https://issues.redhat.com/browse/JBIDE-27135?page=com.atlassian.jira.plug... ]
Zbyněk Červinka updated JBIDE-27135:
------------------------------------
Description:
h2. Details:
* the whole testclass does not run due to issue while adding Java
h2. Error description:
{color:#DE350B}The home directory does not exist.{color}
h2. Terminal output details:
11:14:27.334 INFO [WorkbenchTestable][JRERequirement] JRE Requirement fulfill performed
11:14:27.334 DEBUG [WorkbenchTestable][JRERequirement] Configuration (name,version,path): openjdk-1.8, 1.8, /qa/tools/opt/osx/openjdk-1.8.0
h2. Stacktrace:
{code:java}
java.lang.AssertionError: The following shells remained open [Preferences]
at org.junit.Assert.fail(Assert.java:88)
at org.eclipse.reddeer.junit.extension.after.test.impl.CloseAllShellsExt.run(CloseAllShellsExt.java:79)
at org.eclipse.reddeer.junit.extension.after.test.impl.CloseAllShellsExt.runAfterTestClass(CloseAllShellsExt.java:59)
at org.eclipse.reddeer.junit.internal.runner.statement.RunIAfterClassExtensions.evaluate(RunIAfterClassExtensions.java:71)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:206)
at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:161)
at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:84)
at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:113)
at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.runTests(AbstractUITestApplication.java:44)
at org.eclipse.e4.ui.internal.workbench.swt.E4Testable.lambda$0(E4Testable.java:76)
at java.base/java.lang.Thread.run(Thread.java:834)
{code}
was:
h2. Error description:
The home directory does not exist.
h2. Stacktrace:
{code:java}
java.lang.AssertionError: The following shells remained open [Preferences]
at org.junit.Assert.fail(Assert.java:88)
at org.eclipse.reddeer.junit.extension.after.test.impl.CloseAllShellsExt.run(CloseAllShellsExt.java:79)
at org.eclipse.reddeer.junit.extension.after.test.impl.CloseAllShellsExt.runAfterTestClass(CloseAllShellsExt.java:59)
at org.eclipse.reddeer.junit.internal.runner.statement.RunIAfterClassExtensions.evaluate(RunIAfterClassExtensions.java:71)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:206)
at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:161)
at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:84)
at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:113)
at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.runTests(AbstractUITestApplication.java:44)
at org.eclipse.e4.ui.internal.workbench.swt.E4Testable.lambda$0(E4Testable.java:76)
at java.base/java.lang.Thread.run(Thread.java:834)
{code}
> Fix the failing HTML5Parameterized central.itests testclass on OS X
> -------------------------------------------------------------------
>
> Key: JBIDE-27135
> URL: https://issues.redhat.com/browse/JBIDE-27135
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: integration-tests
> Affects Versions: 4.15.0.AM1
> Reporter: Zbyněk Červinka
> Assignee: Zbyněk Červinka
> Priority: Blocker
>
> h2. Details:
> * the whole testclass does not run due to issue while adding Java
> h2. Error description:
> {color:#DE350B}The home directory does not exist.{color}
> h2. Terminal output details:
> 11:14:27.334 INFO [WorkbenchTestable][JRERequirement] JRE Requirement fulfill performed
> 11:14:27.334 DEBUG [WorkbenchTestable][JRERequirement] Configuration (name,version,path): openjdk-1.8, 1.8, /qa/tools/opt/osx/openjdk-1.8.0
> h2. Stacktrace:
> {code:java}
> java.lang.AssertionError: The following shells remained open [Preferences]
> at org.junit.Assert.fail(Assert.java:88)
> at org.eclipse.reddeer.junit.extension.after.test.impl.CloseAllShellsExt.run(CloseAllShellsExt.java:79)
> at org.eclipse.reddeer.junit.extension.after.test.impl.CloseAllShellsExt.runAfterTestClass(CloseAllShellsExt.java:59)
> at org.eclipse.reddeer.junit.internal.runner.statement.RunIAfterClassExtensions.evaluate(RunIAfterClassExtensions.java:71)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
> 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:206)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:161)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:84)
> at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:113)
> at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.runTests(AbstractUITestApplication.java:44)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Testable.lambda$0(E4Testable.java:76)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (JBIDE-27135) Fix the failing HTML5Parameterized central.itests testclass on OS X
by Zbyněk Červinka (Jira)
Zbyněk Červinka created JBIDE-27135:
---------------------------------------
Summary: Fix the failing HTML5Parameterized central.itests testclass on OS X
Key: JBIDE-27135
URL: https://issues.redhat.com/browse/JBIDE-27135
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: integration-tests
Affects Versions: 4.15.0.AM1
Reporter: Zbyněk Červinka
Assignee: Zbyněk Červinka
h2. Error description:
The home directory does not exist.
h2. Stacktrace:
{code:java}
java.lang.AssertionError: The following shells remained open [Preferences]
at org.junit.Assert.fail(Assert.java:88)
at org.eclipse.reddeer.junit.extension.after.test.impl.CloseAllShellsExt.run(CloseAllShellsExt.java:79)
at org.eclipse.reddeer.junit.extension.after.test.impl.CloseAllShellsExt.runAfterTestClass(CloseAllShellsExt.java:59)
at org.eclipse.reddeer.junit.internal.runner.statement.RunIAfterClassExtensions.evaluate(RunIAfterClassExtensions.java:71)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:206)
at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:161)
at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:84)
at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:113)
at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.runTests(AbstractUITestApplication.java:44)
at org.eclipse.e4.ui.internal.workbench.swt.E4Testable.lambda$0(E4Testable.java:76)
at java.base/java.lang.Thread.run(Thread.java:834)
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (JBIDE-27135) Fix the failing HTML5Parameterized central.itests testclass on OS X
by Zbyněk Červinka (Jira)
[ https://issues.redhat.com/browse/JBIDE-27135?page=com.atlassian.jira.plug... ]
Zbyněk Červinka updated JBIDE-27135:
------------------------------------
Description:
h2. Error description:
The home directory does not exist.
h2. Stacktrace:
{code:java}
java.lang.AssertionError: The following shells remained open [Preferences]
at org.junit.Assert.fail(Assert.java:88)
at org.eclipse.reddeer.junit.extension.after.test.impl.CloseAllShellsExt.run(CloseAllShellsExt.java:79)
at org.eclipse.reddeer.junit.extension.after.test.impl.CloseAllShellsExt.runAfterTestClass(CloseAllShellsExt.java:59)
at org.eclipse.reddeer.junit.internal.runner.statement.RunIAfterClassExtensions.evaluate(RunIAfterClassExtensions.java:71)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:206)
at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:161)
at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:84)
at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:113)
at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.runTests(AbstractUITestApplication.java:44)
at org.eclipse.e4.ui.internal.workbench.swt.E4Testable.lambda$0(E4Testable.java:76)
at java.base/java.lang.Thread.run(Thread.java:834)
{code}
was:
h2. Error description:
The home directory does not exist.
h2. Stacktrace:
{code:java}
java.lang.AssertionError: The following shells remained open [Preferences]
at org.junit.Assert.fail(Assert.java:88)
at org.eclipse.reddeer.junit.extension.after.test.impl.CloseAllShellsExt.run(CloseAllShellsExt.java:79)
at org.eclipse.reddeer.junit.extension.after.test.impl.CloseAllShellsExt.runAfterTestClass(CloseAllShellsExt.java:59)
at org.eclipse.reddeer.junit.internal.runner.statement.RunIAfterClassExtensions.evaluate(RunIAfterClassExtensions.java:71)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:206)
at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:161)
at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:84)
at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:113)
at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.runTests(AbstractUITestApplication.java:44)
at org.eclipse.e4.ui.internal.workbench.swt.E4Testable.lambda$0(E4Testable.java:76)
at java.base/java.lang.Thread.run(Thread.java:834)
{code}
> Fix the failing HTML5Parameterized central.itests testclass on OS X
> -------------------------------------------------------------------
>
> Key: JBIDE-27135
> URL: https://issues.redhat.com/browse/JBIDE-27135
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: integration-tests
> Affects Versions: 4.15.0.AM1
> Reporter: Zbyněk Červinka
> Assignee: Zbyněk Červinka
> Priority: Blocker
>
> h2. Error description:
> The home directory does not exist.
> h2. Stacktrace:
> {code:java}
> java.lang.AssertionError: The following shells remained open [Preferences]
> at org.junit.Assert.fail(Assert.java:88)
> at org.eclipse.reddeer.junit.extension.after.test.impl.CloseAllShellsExt.run(CloseAllShellsExt.java:79)
> at org.eclipse.reddeer.junit.extension.after.test.impl.CloseAllShellsExt.runAfterTestClass(CloseAllShellsExt.java:59)
> at org.eclipse.reddeer.junit.internal.runner.statement.RunIAfterClassExtensions.evaluate(RunIAfterClassExtensions.java:71)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
> 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:206)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:161)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:84)
> at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:113)
> at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.runTests(AbstractUITestApplication.java:44)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Testable.lambda$0(E4Testable.java:76)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (JBIDE-27133) WildFly quickstart 'logging-tools' shows errors after build and import into CodeReady Studio
by Zbyněk Červinka (Jira)
Zbyněk Červinka created JBIDE-27133:
---------------------------------------
Summary: WildFly quickstart 'logging-tools' shows errors after build and import into CodeReady Studio
Key: JBIDE-27133
URL: https://issues.redhat.com/browse/JBIDE-27133
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: project-examples
Affects Versions: 4.15.0.AM1
Reporter: Zbyněk Červinka
Red Hat CodeReady Studio version:
Version: 12.14.0.GA
Build id: GA-v20200321-1015-B6094
Build date: 20200321-1015
{code:java}
Description Resource Path Location Type
The import javax.annotation.processing.Generated cannot be resolved GreetingMessagesBundle_$bundle_de.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/messages line 5 Java Problem
The import javax.annotation.processing.Generated cannot be resolved GreetingMessagesBundle_$bundle_de_DE.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/messages line 5 Java Problem
The import javax.annotation.processing.Generated cannot be resolved GreetingMessagesBundle_$bundle_fr.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/messages line 5 Java Problem
The import javax.annotation.processing.Generated cannot be resolved GreetingMessagesBundle_$bundle_fr_FR.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/messages line 5 Java Problem
The import javax.annotation.processing.Generated cannot be resolved GreetingMessagesBundle_$bundle_sv.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/messages line 5 Java Problem
The import javax.annotation.processing.Generated cannot be resolved GreetingMessagesBundle_$bundle_sv_SE.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/messages line 5 Java Problem
Generated cannot be resolved to a type GreetingMessagesBundle_$bundle_de.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/messages line 10 Java Problem
Generated cannot be resolved to a type GreetingMessagesBundle_$bundle_de_DE.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/messages line 10 Java Problem
Generated cannot be resolved to a type GreetingMessagesBundle_$bundle_fr.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/messages line 10 Java Problem
Generated cannot be resolved to a type GreetingMessagesBundle_$bundle_fr_FR.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/messages line 10 Java Problem
Generated cannot be resolved to a type GreetingMessagesBundle_$bundle_sv.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/messages line 10 Java Problem
Generated cannot be resolved to a type GreetingMessagesBundle_$bundle_sv_SE.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/messages line 10 Java Problem
The import javax.annotation.processing.Generated cannot be resolved DateLogger_$logger_de.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/loggers line 5 Java Problem
The import javax.annotation.processing.Generated cannot be resolved DateLogger_$logger_de_DE.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/loggers line 5 Java Problem
The import javax.annotation.processing.Generated cannot be resolved DateLogger_$logger_fr.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/loggers line 5 Java Problem
The import javax.annotation.processing.Generated cannot be resolved DateLogger_$logger_fr_FR.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/loggers line 5 Java Problem
The import javax.annotation.processing.Generated cannot be resolved DateLogger_$logger_sv.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/loggers line 5 Java Problem
The import javax.annotation.processing.Generated cannot be resolved DateLogger_$logger_sv_SE.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/loggers line 5 Java Problem
The import javax.annotation.processing.Generated cannot be resolved GreeterLogger_$logger_de.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/loggers line 5 Java Problem
The import javax.annotation.processing.Generated cannot be resolved GreeterLogger_$logger_de_DE.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/loggers line 5 Java Problem
The import javax.annotation.processing.Generated cannot be resolved GreeterLogger_$logger_fr.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/loggers line 5 Java Problem
The import javax.annotation.processing.Generated cannot be resolved GreeterLogger_$logger_fr_FR.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/loggers line 5 Java Problem
The import javax.annotation.processing.Generated cannot be resolved GreeterLogger_$logger_sv.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/loggers line 5 Java Problem
The import javax.annotation.processing.Generated cannot be resolved GreeterLogger_$logger_sv_SE.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/loggers line 5 Java Problem
Generated cannot be resolved to a type DateLogger_$logger_de.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/loggers line 11 Java Problem
Generated cannot be resolved to a type DateLogger_$logger_de_DE.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/loggers line 11 Java Problem
Generated cannot be resolved to a type DateLogger_$logger_fr.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/loggers line 11 Java Problem
Generated cannot be resolved to a type DateLogger_$logger_fr_FR.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/loggers line 11 Java Problem
Generated cannot be resolved to a type DateLogger_$logger_sv.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/loggers line 11 Java Problem
Generated cannot be resolved to a type DateLogger_$logger_sv_SE.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/loggers line 11 Java Problem
Generated cannot be resolved to a type GreeterLogger_$logger_de.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/loggers line 11 Java Problem
Generated cannot be resolved to a type GreeterLogger_$logger_de_DE.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/loggers line 11 Java Problem
Generated cannot be resolved to a type GreeterLogger_$logger_fr.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/loggers line 11 Java Problem
Generated cannot be resolved to a type GreeterLogger_$logger_fr_FR.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/loggers line 11 Java Problem
Generated cannot be resolved to a type GreeterLogger_$logger_sv.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/loggers line 11 Java Problem
Generated cannot be resolved to a type GreeterLogger_$logger_sv_SE.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/loggers line 11 Java Problem
The import javax.annotation.processing.Generated cannot be resolved DateExceptionsBundle_$bundle_de.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/exceptions line 5 Java Problem
The import javax.annotation.processing.Generated cannot be resolved DateExceptionsBundle_$bundle_de_DE.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/exceptions line 5 Java Problem
The import javax.annotation.processing.Generated cannot be resolved DateExceptionsBundle_$bundle_fr.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/exceptions line 5 Java Problem
The import javax.annotation.processing.Generated cannot be resolved DateExceptionsBundle_$bundle_fr_FR.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/exceptions line 5 Java Problem
The import javax.annotation.processing.Generated cannot be resolved DateExceptionsBundle_$bundle_sv.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/exceptions line 5 Java Problem
The import javax.annotation.processing.Generated cannot be resolved DateExceptionsBundle_$bundle_sv_SE.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/exceptions line 5 Java Problem
The import javax.annotation.processing.Generated cannot be resolved GreeterExceptionBundle_$bundle_de.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/exceptions line 5 Java Problem
The import javax.annotation.processing.Generated cannot be resolved GreeterExceptionBundle_$bundle_de_DE.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/exceptions line 5 Java Problem
The import javax.annotation.processing.Generated cannot be resolved GreeterExceptionBundle_$bundle_fr.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/exceptions line 5 Java Problem
The import javax.annotation.processing.Generated cannot be resolved GreeterExceptionBundle_$bundle_fr_FR.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/exceptions line 5 Java Problem
The import javax.annotation.processing.Generated cannot be resolved GreeterExceptionBundle_$bundle_sv.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/exceptions line 5 Java Problem
The import javax.annotation.processing.Generated cannot be resolved GreeterExceptionBundle_$bundle_sv_SE.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/exceptions line 5 Java Problem
Generated cannot be resolved to a type DateExceptionsBundle_$bundle_de.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/exceptions line 10 Java Problem
Generated cannot be resolved to a type DateExceptionsBundle_$bundle_de_DE.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/exceptions line 10 Java Problem
Generated cannot be resolved to a type DateExceptionsBundle_$bundle_fr.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/exceptions line 10 Java Problem
Generated cannot be resolved to a type DateExceptionsBundle_$bundle_fr_FR.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/exceptions line 10 Java Problem
Generated cannot be resolved to a type DateExceptionsBundle_$bundle_sv.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/exceptions line 10 Java Problem
Generated cannot be resolved to a type DateExceptionsBundle_$bundle_sv_SE.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/exceptions line 10 Java Problem
Generated cannot be resolved to a type GreeterExceptionBundle_$bundle_de.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/exceptions line 10 Java Problem
Generated cannot be resolved to a type GreeterExceptionBundle_$bundle_de_DE.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/exceptions line 10 Java Problem
Generated cannot be resolved to a type GreeterExceptionBundle_$bundle_fr.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/exceptions line 10 Java Problem
Generated cannot be resolved to a type GreeterExceptionBundle_$bundle_fr_FR.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/exceptions line 10 Java Problem
Generated cannot be resolved to a type GreeterExceptionBundle_$bundle_sv.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/exceptions line 10 Java Problem
Generated cannot be resolved to a type GreeterExceptionBundle_$bundle_sv_SE.java /logging-tools/target/generated-sources/annotations/org/jboss/as/quickstarts/loggingToolsQS/exceptions line 10 Java Problem
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (JBIDE-27132) WildFly quickstart 'country-client' shows errors after import
by Zbyněk Červinka (Jira)
[ https://issues.redhat.com/browse/JBIDE-27132?page=com.atlassian.jira.plug... ]
Zbyněk Červinka updated JBIDE-27132:
------------------------------------
Description:
WildFly quickstart 'country-client' shows errors after import:
* Multiple JAX-RS Activators are defined for the project.
file: /country-client/src/test/java/org/wildfly/quickstarts/microprofile/rest/client/api/JaxRsApplication.java
* Multiple JAX-RS Activators are defined for the project.
file: /country-client/src/main/java/org/wildfly/quickstarts/microprofile/rest/client/JaxRsApplication.java
was:
WildFly quickstart 'country-client' shows errors after import:
* Multiple JAX-RS Activators are defined for the project.
/country-client/src/test/java/org/wildfly/quickstarts/microprofile/rest/client/api/JaxRsApplication.java
* Multiple JAX-RS Activators are defined for the project.
/country-client/src/main/java/org/wildfly/quickstarts/microprofile/rest/client/JaxRsApplication.java
> WildFly quickstart 'country-client' shows errors after import
> -------------------------------------------------------------
>
> Key: JBIDE-27132
> URL: https://issues.redhat.com/browse/JBIDE-27132
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.15.0.AM1
> Reporter: Zbyněk Červinka
> Priority: Major
>
> WildFly quickstart 'country-client' shows errors after import:
> * Multiple JAX-RS Activators are defined for the project.
> file: /country-client/src/test/java/org/wildfly/quickstarts/microprofile/rest/client/api/JaxRsApplication.java
> * Multiple JAX-RS Activators are defined for the project.
> file: /country-client/src/main/java/org/wildfly/quickstarts/microprofile/rest/client/JaxRsApplication.java
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (JBIDE-27132) WildFly quickstart 'country-client' shows errors after import
by Zbyněk Červinka (Jira)
Zbyněk Červinka created JBIDE-27132:
---------------------------------------
Summary: WildFly quickstart 'country-client' shows errors after import
Key: JBIDE-27132
URL: https://issues.redhat.com/browse/JBIDE-27132
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: project-examples
Affects Versions: 4.15.0.AM1
Reporter: Zbyněk Červinka
WildFly quickstart 'country-client' shows errors after import:
* Multiple JAX-RS Activators are defined for the project.
/country-client/src/test/java/org/wildfly/quickstarts/microprofile/rest/client/api/JaxRsApplication.java
* Multiple JAX-RS Activators are defined for the project.
/country-client/src/main/java/org/wildfly/quickstarts/microprofile/rest/client/JaxRsApplication.java
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years