December 2017 - jbosstools-issues

[JBoss JIRA] (JBDS-4638) Failing tests for quickstarts [jts][ejb-security-interceptors] on WildFly-11

by Vojtech Prusa (JIRA)

[ https://issues.jboss.org/browse/JBDS-4638?page=com.atlassian.jira.plugin.... ] Vojtech Prusa updated JBDS-4638: -------------------------------- Description: Automation fails because of error (manually tested in attachment) for this quickstart. https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... and https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... I suppose this error is duplicate to: https://bugzilla.redhat.com/show_bug.cgi?id=1192591 Using mentioned workaround I get: Description Resource Path Location Type Referenced file contains errors (jar:file:~/ws/devstudio-11.2.0.AM2-v20171210-2039-B1746/studio/plugins/org.jboss.tools.as.catalog_3.5.2.v20171114-2016.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..." jboss-ejb3.xml /jts-application-component-2/src/main/resources/META-INF line 1 XML Problem What I did to get rid of this error message was removing from xsi:schemaLocation string "http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd" thought i think this is wrong approach and i did not deploy this quickstart yet. Please make a comment [~wolfc] [~rob.stryker] [~sgilda] Thank you. was: Automation fails because of error (manually tested in attachment) for this quickstart. https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... and https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... I suppose this error is duplicate to: https://bugzilla.redhat.com/show_bug.cgi?id=1192591 Using mentioned workaround I get: Description Resource Path Location Type Referenced file contains errors (jar:file:~/ws/devstudio-11.2.0.AM2-v20171210-2039-B1746/studio/plugins/org.jboss.tools.as.catalog_3.5.2.v20171114-2016.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..." jboss-ejb3.xml /jts-application-component-2/src/main/resources/META-INF line 1 XML Problem What did get rid of the error message was removing from xsi:schemaLocation string "http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd" thought i think this is wrong approach and i did not deploy this quickstart yet. Please make a comment [~wolfc] [~rob.stryker] [~sgilda] Thank you. > Failing tests for quickstarts [jts][ejb-security-interceptors] on WildFly-11 > ---------------------------------------------------------------------------- > > Key: JBDS-4638 > URL: https://issues.jboss.org/browse/JBDS-4638 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: project-examples > Affects Versions: 11.2.0.AM2 > Environment: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... > Server: WF11 > Quickstart: 11.x > Reporter: Vojtech Prusa > Attachments: jts.errors.txt > > > Automation fails because of error (manually tested in attachment) for this quickstart. > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... > and > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... > I suppose this error is duplicate to: > https://bugzilla.redhat.com/show_bug.cgi?id=1192591 > Using mentioned workaround I get: > Description Resource Path Location Type > Referenced file contains errors (jar:file:~/ws/devstudio-11.2.0.AM2-v20171210-2039-B1746/studio/plugins/org.jboss.tools.as.catalog_3.5.2.v20171114-2016.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..." jboss-ejb3.xml /jts-application-component-2/src/main/resources/META-INF line 1 XML Problem > What I did to get rid of this error message was removing from xsi:schemaLocation string "http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd" > thought i think this is wrong approach and i did not deploy this quickstart yet. > Please make a comment > [~wolfc] [~rob.stryker] [~sgilda] > Thank you. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4636) Failing tests for quickstart [spring-petclinic] on WildFly-11

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/JBDS-4636?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on JBDS-4636: ----------------------------------- I don't mind dropping spring-petclinic QS from EAP Quick starts As [~trepel] says it is quite outdated and we do not keep it in line with upstream version. It might be worth looking into providing some other guideline how to deploy petclinic on EAP in context of OpenShift so we still have the added value on how to deploy it, but shipping it as part of our product quickstarts is probably not needed anymore. > Failing tests for quickstart [spring-petclinic] on WildFly-11 > ------------------------------------------------------------- > > Key: JBDS-4636 > URL: https://issues.jboss.org/browse/JBDS-4636 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: project-examples > Affects Versions: 11.2.0.AM2 > Environment: jdk=jdk1.8,label=fedora26 > jdk=jdk1.8,label=ubuntu1704 > jdk=openjdk-1.8,label=fedora26 > jdk=openjdk-1.8,label=win10 > Server: WF11 > Quickstarts: 11.x > Reporter: Vojtech Prusa > Attachments: spring-petclinic.errors.txt > > > There are JavaScript related errors in JBDS for which automation fails. > Related test reports: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... > Test results: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... > I think there may be some other configuration for JavaScript support necessary. > I was successful at deploying this quickstart. > Errors bothering me most are: > ')' expected intro.js /spring-petclinic/src/main/webapp/vendors/jquery/src line 20 > and > The element type "meta" must be terminated by the matching end-tag "</meta>". > I have added Spring IDE plugin to JBDS but I still get same errors. > Please comment [~n1hility] [~ctomc] [~trepel] [~sgilda] > Thank you. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1195) invalid children in composite sites listed on ide-config.properties

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1195?page=com.atlassian.jira.plugin... ] Andrej Podhradsky closed JBTIS-1195. ------------------------------------ Verified, now we have a green job https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > invalid children in composite sites listed on ide-config.properties > ------------------------------------------------------------------- > > Key: JBTIS-1195 > URL: https://issues.jboss.org/browse/JBTIS-1195 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: build, releng > Affects Versions: 4.5.1.Beta1b > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.5.1.CR1 > > > I recently wrote a URL checker [1] for ide-config.properties to see if all the linked sites are valid. > [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Turns out... we have some 404s in there. > {code}23:15:43 [INFO] Checking for valid children in: http://download.jboss.org/jbosstools/updates/stable/luna/integration-stac... > 23:15:45 {24/45} [3/3] > > http://download.jboss.org/jbosstools/updates/stable/luna/integration-stac... : NOT FOUND > > 23:17:39 [INFO] Checking for valid children in: https://devstudio.redhat.com/updates/8.0/integration-stack/extras//compos... > 23:17:44 {45/45} [3/3] > > https://devstudio.redhat.com/updates/8.0/integration-stack/extras//jboss-... : NOT FOUND{code} > Both of these seem to be caused by the fact that there are update sites (which are NOT composites) but which have compositeContent.xml files in them. > 1. http://download.jboss.org/jbosstools/updates/stable/luna/integration-stac... should not exist, since http://download.jboss.org/jbosstools/updates/stable/luna/integration-stac... has its own content.jar and artifacts.jar > 2. https://devstudio.redhat.com/updates/8.0/integration-stack/extras//jboss-... should not esxit, since https://devstudio.redhat.com/updates/8.0/integration-stack/extras//jboss-... has its own content.jar and artifacts.jar -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4637) Failing quickstart WildFly-11 [template]

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBDS-4637?page=com.atlassian.jira.plugin.... ] Josef Kopriva commented on JBDS-4637: ------------------------------------- [~vprusa] we can exclude it :) > Failing quickstart WildFly-11 [template] > ---------------------------------------- > > Key: JBDS-4637 > URL: https://issues.jboss.org/browse/JBDS-4637 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: project-examples > Affects Versions: 11.2.0.AM2 > Environment: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... > WF11 > quickstartes 11.0.0.Final > Reporter: Vojtech Prusa > Assignee: Vojtech Prusa > Attachments: pom.xml > > > Automation fails because of error after template project is imported. > Test report: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... > Solutions: > https://stackoverflow.com/questions/31835033/web-xml-is-missing-and-failo... > Updated pom.xml as attachment does no show errors after Project Maven -> Update project .. > Idk if right solution is to change pom or generate web.xml with "Java EE Tools -> Generate Deployment Descriptor Stub" in test. > Please comment recommendations [~n1hility] [~ctomc] [~trepel] [~sgilda] [~jkopriva] > Thank you. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4637) Failing quickstart WildFly-11 [template]

by Vojtech Prusa (JIRA)

[ https://issues.jboss.org/browse/JBDS-4637?page=com.atlassian.jira.plugin.... ] Vojtech Prusa commented on JBDS-4637: ------------------------------------- [~ ctomc] Because the integration tests download the entire repo as zip and then import each folder / quickstart as Maven -> Import -> Existing project, this process does not distinguish if it should be buildable just verifies that the project is importable and imported without errors. So I suggest exclude "template" from integration tests, because if valid errors would occur, errors in "template" would be duplicates. What do you think [jkopriva]? > Failing quickstart WildFly-11 [template] > ---------------------------------------- > > Key: JBDS-4637 > URL: https://issues.jboss.org/browse/JBDS-4637 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: project-examples > Affects Versions: 11.2.0.AM2 > Environment: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... > WF11 > quickstartes 11.0.0.Final > Reporter: Vojtech Prusa > Assignee: Vojtech Prusa > Attachments: pom.xml > > > Automation fails because of error after template project is imported. > Test report: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... > Solutions: > https://stackoverflow.com/questions/31835033/web-xml-is-missing-and-failo... > Updated pom.xml as attachment does no show errors after Project Maven -> Update project .. > Idk if right solution is to change pom or generate web.xml with "Java EE Tools -> Generate Deployment Descriptor Stub" in test. > Please comment recommendations [~n1hility] [~ctomc] [~trepel] [~sgilda] [~jkopriva] > Thank you. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4638) Failing tests for quickstarts [jts][ejb-security-interceptors] on WildFly-11

by Vojtech Prusa (JIRA)

[ https://issues.jboss.org/browse/JBDS-4638?page=com.atlassian.jira.plugin.... ] Vojtech Prusa commented on JBDS-4638: ------------------------------------- Looking finto this further, according to https://github.com/jboss-developer/jboss-developer-shared-resources/blob/... we should ignore this error, i would add skip for this error in tests [~jkopriva] . > Failing tests for quickstarts [jts][ejb-security-interceptors] on WildFly-11 > ---------------------------------------------------------------------------- > > Key: JBDS-4638 > URL: https://issues.jboss.org/browse/JBDS-4638 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: project-examples > Affects Versions: 11.2.0.AM2 > Environment: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... > Server: WF11 > Quickstart: 11.x > Reporter: Vojtech Prusa > Attachments: jts.errors.txt > > > Automation fails because of error (manually tested in attachment) for this quickstart. > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... > and > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... > I suppose this error is duplicate to: > https://bugzilla.redhat.com/show_bug.cgi?id=1192591 > Using mentioned workaround I get: > Description Resource Path Location Type > Referenced file contains errors (jar:file:~/ws/devstudio-11.2.0.AM2-v20171210-2039-B1746/studio/plugins/org.jboss.tools.as.catalog_3.5.2.v20171114-2016.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..." jboss-ejb3.xml /jts-application-component-2/src/main/resources/META-INF line 1 XML Problem > What did get rid of the error message was removing from xsi:schemaLocation string "http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd" > thought i think this is wrong approach and i did not deploy this quickstart yet. > Please make a comment > [~wolfc] [~rob.stryker] [~sgilda] > Thank you. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4636) Failing tests for quickstart [spring-petclinic] on WildFly-11

by Vojtech Prusa (JIRA)

[ https://issues.jboss.org/browse/JBDS-4636?page=com.atlassian.jira.plugin.... ] Vojtech Prusa commented on JBDS-4636: ------------------------------------- [~sgilda] i think src/main/webapp/vendors/jquery/src/inro.js is part of js template and src/main/webapp/vendors/jquery/src/outro.js is other part or one of other parts. Imo nicer way would be use functions/methods and not syntax breaking spreading code blocks in several files. [~trepel] If that is the case then i could a) add this test to blacklist for the time being. b) add skip specific errors. What do you think [~jkopriva] ? > Failing tests for quickstart [spring-petclinic] on WildFly-11 > ------------------------------------------------------------- > > Key: JBDS-4636 > URL: https://issues.jboss.org/browse/JBDS-4636 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: project-examples > Affects Versions: 11.2.0.AM2 > Environment: jdk=jdk1.8,label=fedora26 > jdk=jdk1.8,label=ubuntu1704 > jdk=openjdk-1.8,label=fedora26 > jdk=openjdk-1.8,label=win10 > Server: WF11 > Quickstarts: 11.x > Reporter: Vojtech Prusa > Attachments: spring-petclinic.errors.txt > > > There are JavaScript related errors in JBDS for which automation fails. > Related test reports: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... > Test results: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... > I think there may be some other configuration for JavaScript support necessary. > I was successful at deploying this quickstart. > Errors bothering me most are: > ')' expected intro.js /spring-petclinic/src/main/webapp/vendors/jquery/src line 20 > and > The element type "meta" must be terminated by the matching end-tag "</meta>". > I have added Spring IDE plugin to JBDS but I still get same errors. > Please comment [~n1hility] [~ctomc] [~trepel] [~sgilda] > Thank you. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25515) GetJBDSInstallerLink.groovy scripts has no permissions to use some features of Jenkins API

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25515?page=com.atlassian.jira.plugi... ] Lukáš Valach commented on JBIDE-25515: -------------------------------------- I avoided a security restrictions using [Scriptler Plugin|https://wiki.jenkins.io/display/JENKINS/Scriptler+Plugin]. GetJBDSInstallerLink.groovy is stored at Jenkins and may be executed using "Scriptlet script" build step. > GetJBDSInstallerLink.groovy scripts has no permissions to use some features of Jenkins API > ------------------------------------------------------------------------------------------ > > Key: JBIDE-25515 > URL: https://issues.jboss.org/browse/JBIDE-25515 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Affects Versions: 4.5.2.AM3 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.5.2.AM3 > > > A lot of installer tests are failing because after last update of Jenkins script \[1\] GetJBDSInstallerLink.groovy hasn't permission to use some features of Jenkins API. > \[1\] https://github.com/jbdevstudio/jbdevstudio-qa/blob/master/jenkins-script/... > There is this error message in the log: > {code} > ERROR: Build step failed with exception > org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use new java.util.HashMap > {code} > The rights were limited for a security reason so I need to findout a workaround. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25515) GetJBDSInstallerLink.groovy scripts has no permissions to use some features of Jenkins API

by Lukáš Valach (JIRA)

Lukáš Valach created JBIDE-25515: ------------------------------------ Summary: GetJBDSInstallerLink.groovy scripts has no permissions to use some features of Jenkins API Key: JBIDE-25515 URL: https://issues.jboss.org/browse/JBIDE-25515 Project: Tools (JBoss Tools) Issue Type: Bug Components: qa Affects Versions: 4.5.2.AM3 Reporter: Lukáš Valach Assignee: Lukáš Valach Fix For: 4.5.2.AM3 A lot of installer tests are failing because after last update of Jenkins script \[1\] GetJBDSInstallerLink.groovy hasn't permission to use some features of Jenkins API. \[1\] https://github.com/jbdevstudio/jbdevstudio-qa/blob/master/jenkins-script/... There is this error message in the log: {code} ERROR: Build step failed with exception org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use new java.util.HashMap {code} The rights were limited for a security reason so I need to findout a workaround. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24754) Redhat central screen doesnt show due to JS error

by Vojtech Prusa (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24754?page=com.atlassian.jira.plugi... ] Vojtech Prusa closed JBIDE-24754. --------------------------------- Resolution: Done > Redhat central screen doesnt show due to JS error > ------------------------------------------------- > > Key: JBIDE-24754 > URL: https://issues.jboss.org/browse/JBIDE-24754 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Affects Versions: 4.5.0.AM1 > Reporter: Anton Hughes > Assignee: Vojtech Prusa > Fix For: 4.5.2.AM3 > > > I am trying to run the latest Jboss Tools (Oxygen) on Ubuntu 17.04. > h2. Eclipse Version > Eclipse Java EE IDE for Web Developers. > Version: Oxygen Release (4.7.0) > Build id: 20170620-1800 > h2. Stacktrace > {code:java} > org.eclipse.swt.SWTException: An exception was raised in JavaScript > at org.eclipse.swt.browser.WebKit$Webkit2JavascriptEvaluator.evaluate(WebKit.java:1273) > at org.eclipse.swt.browser.WebKit.evaluate(WebKit.java:1324) > at org.eclipse.swt.browser.WebBrowser.evaluate(WebBrowser.java:409) > at org.eclipse.swt.browser.Browser.evaluate(Browser.java:663) > at org.eclipse.swt.browser.Browser.evaluate(Browser.java:610) > at org.jboss.tools.central.internal.browser.VersionedBrowser.<init>(VersionedBrowser.java:51) > at org.jboss.tools.central.editors.GettingStartedHtmlPage.createBrowserSection(GettingStartedHtmlPage.java:188) > at org.jboss.tools.central.editors.GettingStartedHtmlPage.createFormContent(GettingStartedHtmlPage.java:175) > at org.eclipse.ui.forms.editor.FormPage.lambda$0(FormPage.java:163) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.ui.forms.editor.FormPage.createPartControl(FormPage.java:163) > at org.eclipse.ui.forms.editor.FormEditor.pageChange(FormEditor.java:480) > at org.eclipse.ui.part.MultiPageEditorPart.setActivePage(MultiPageEditorPart.java:1077) > at org.eclipse.ui.forms.editor.FormEditor.setActivePage(FormEditor.java:614) > at org.eclipse.ui.forms.editor.SharedHeaderFormEditor.createPages(SharedHeaderFormEditor.java:106) > at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:348) > at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:151) > at org.eclipse.ui.internal.e4.compatibility.CompatibilityEditor.createPartControl(CompatibilityEditor.java:99) > at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:355) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55) > at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:990) > at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:955) > at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:124) > at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:399) > at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:318) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162) > at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:105) > at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:74) > at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:56) > at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:129) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:997) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:666) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:772) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:743) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:737) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:721) > at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer.showTab(StackRenderer.java:1289) > at org.eclipse.e4.ui.workbench.renderers.swt.LazyStackRenderer.lambda$0(LazyStackRenderer.java:68) > at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:40) > at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:233) > at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:144) > at org.eclipse.swt.widgets.Display.syncExec(Display.java:5439) > at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:212) > at org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:36) > at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:201) > at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197) > at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1) > at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) > at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148) > at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135) > at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78) > at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39) > at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:52) > at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:60) > at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374) > at org.eclipse.e4.ui.model.application.ui.impl.ElementContainerImpl.setSelectedElement(ElementContainerImpl.java:173) > at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.showElementInWindow(ModelServiceImpl.java:620) > at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:584) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.delegateBringToTop(PartServiceImpl.java:768) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.bringToTop(PartServiceImpl.java:401) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1187) > at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:3261) > at org.eclipse.ui.internal.WorkbenchPage.access$25(WorkbenchPage.java:3176) > at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:3158) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3153) > at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3117) > at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3098) > at org.jboss.tools.central.JBossCentralActivator.openJBossCentralEditor(JBossCentralActivator.java:437) > at org.jboss.tools.central.JBossCentralActivator.getJBossCentralEditor(JBossCentralActivator.java:425) > at org.jboss.tools.central.ShowJBossCentral$2.run(ShowJBossCentral.java:110) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:37) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4497) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4110) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1155) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1044) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153) > at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590) > at org.eclipse.equinox.launcher.Main.run(Main.java:1499) > at org.eclipse.equinox.launcher.Main.main(Main.java:1472) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2017