[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)
8 years
[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)
8 years
[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)
8 years
[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 updated JBIDE-24754:
----------------------------------
Fix Version/s: 4.5.2.AM3
(was: 4.5.x)
> 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)
8 years
[JBoss JIRA] (JBDS-4636) Failing tests for quickstart [spring-petclinic] on WildFly-11
by Tomas Repel (JIRA)
[ https://issues.jboss.org/browse/JBDS-4636?page=com.atlassian.jira.plugin.... ]
Tomas Repel commented on JBDS-4636:
-----------------------------------
Hi [~sgilda],
the git repo url: https://github.com/spring-projects/spring-petclinic
You can see I did few small contributions back in 2015. The intention was to make it run on JBoss/EAP more smoothly. But since the spring-petclinic is not being maintained for some time now I can imagine our code and their code diverged a lot.
I am not in EAP QE so I don't follow what was happening closely enough but were there any conclusion what quickstarts would be removed in EAP 7.2 if any? I would consider this one to be a good candidate :)
> 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)
8 years
[JBoss JIRA] (JBIDE-25455) JBoss Tools marketplace listing includes org.eclipse features
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25455?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-25455:
---------------------------------------------
btw. i just noticed the image - yeah, all of those not just buildship has nothing to do on our marketplace entry.
> JBoss Tools marketplace listing includes org.eclipse features
> -------------------------------------------------------------
>
> Key: JBIDE-25455
> URL: https://issues.jboss.org/browse/JBIDE-25455
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: marketplace
> Affects Versions: 4.5.1.Final
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Fix For: 4.5.2.Final
>
> Attachments: jbosstools-eclipse-plugins-marketplace.png
>
>
> Someone added org.eclipse.buildship and org.eclipse.wst.* features to the Marketplace listing as optional-selected features.
> Shouldn't these be installed via requirements from JBT features, and therefore not needed on the site?
> The list of sanctioned features in the CoreTools category on the JBT site is here:
> http://download.jboss.org/jbosstools/static/oxygen/stable/updates/core/4....
> So... why did the other features get added? And if they SHOULD be there, they should also be added to the JBT site too, for consistency. Right?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (JBIDE-25455) JBoss Tools marketplace listing includes org.eclipse features
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25455?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen edited comment on JBIDE-25455 at 12/19/17 6:51 PM:
-----------------------------------------------------------------------
Whether something is in the JEE package has had no bearing on whether it should be on jbosstools or devstudio marketplace entries. We treat all those parts (WTP, m2e, etc.) as separate things anyways.
"We'll include Buildship as a 1rst class citizen in JBT and devstudio, as we do with maven." - I don't see m2e listed as a first level feature to install. So buildship has no reason to be listed there.
it should just be in the list of mirrored plugins and available from Central as something to install.
was (Author: maxandersen):
Whether something is in the JEE package has had no bearing on whether it should be on jbosstools or devstudio marketplace entries. We treat all those parts (WTP, m2e, etc.) as separate things anyways.
"We'll include Buildship as a 1rst class citizen in JBT and devstudio, as we do with maven." - I don't see m2e listed as a first level feature to install. So buildship has no reason to be there.
> JBoss Tools marketplace listing includes org.eclipse features
> -------------------------------------------------------------
>
> Key: JBIDE-25455
> URL: https://issues.jboss.org/browse/JBIDE-25455
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: marketplace
> Affects Versions: 4.5.1.Final
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Fix For: 4.5.2.Final
>
> Attachments: jbosstools-eclipse-plugins-marketplace.png
>
>
> Someone added org.eclipse.buildship and org.eclipse.wst.* features to the Marketplace listing as optional-selected features.
> Shouldn't these be installed via requirements from JBT features, and therefore not needed on the site?
> The list of sanctioned features in the CoreTools category on the JBT site is here:
> http://download.jboss.org/jbosstools/static/oxygen/stable/updates/core/4....
> So... why did the other features get added? And if they SHOULD be there, they should also be added to the JBT site too, for consistency. Right?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years