[JBoss JIRA] (JBIDE-27160) XML Editor broken in Eclipse 2020-03 ?
by Thomas Kernstock (Jira)
[ https://issues.redhat.com/browse/JBIDE-27160?page=com.atlassian.jira.plug... ]
Thomas Kernstock commented on JBIDE-27160:
------------------------------------------
Hi Ondrej,
I just switched to the 4.15 Updatesite and installed the new version. The editor problems are gone - everything works fine until now.
Thanxs and br
Thomas
> XML Editor broken in Eclipse 2020-03 ?
> --------------------------------------
>
> Key: JBIDE-27160
> URL: https://issues.redhat.com/browse/JBIDE-27160
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: xml-structured-editor
> Affects Versions: 4.14.0.Final
> Reporter: Thomas Kernstock
> Priority: Major
>
> Hi Guys,
> I hope this is the right place to post this issue.
> I Upgraded to eclipse 2030-03 and installed JBoss Tools from the marketplace - version 4.14.0, using the CDI, Deltaspike, JSF and Webpageeditor. I'm running eclipse on Windows 10 under Oracle JDK 8.
> After createing a fresh workspace and a new CDI Project, i'm not able to open any xml file with the JBoss XML Editor. In the errorlog I find the following stack trace:
> org.eclipse.swt.SWTError: Cannot initialize Drop
> at org.eclipse.swt.dnd.DND.error(DND.java:281)
> at org.eclipse.swt.dnd.DND.error(DND.java:241)
> at org.eclipse.swt.dnd.DropTarget.<init>(DropTarget.java:138)
> at org.jboss.tools.common.model.ui.texteditors.xmleditor.XMLTextEditor.createDrop(XMLTextEditor.java:487)
> at org.jboss.tools.common.model.ui.texteditors.xmleditor.XMLTextEditor.createPartControl(XMLTextEditor.java:151)
> at org.jboss.tools.common.model.ui.texteditors.XMLTextEditorComponent.createPartControl(XMLTextEditorComponent.java:100)
> at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:227)
> at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:203)
> at org.jboss.tools.common.editor.ObjectMultiPageEditor.createTextPage(ObjectMultiPageEditor.java:287)
> at org.jboss.tools.jst.web.ui.editors.WebCompoundEditor.doCreatePages(WebCompoundEditor.java:39)
> at org.jboss.tools.common.editor.ObjectMultiPageEditor.createPages(ObjectMultiPageEditor.java:250)
> at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:333)
> at org.jboss.tools.common.model.ui.editor.EditorPartWrapper.createPartControl(EditorPartWrapper.java:176)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:154)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityEditor.createPartControl(CompatibilityEditor.java:96)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:361)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:58)
> at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:1002)
> at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:967)
> at org.eclipse.e4.core.internal.di.InjectorImpl.internalInject(InjectorImpl.java:139)
> at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:408)
> at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:331)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:202)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:91)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:60)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:42)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:132)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:1002)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:662)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:768)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:739)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:733)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:717)
> at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer.showTab(StackRenderer.java:1297)
> at org.eclipse.e4.ui.workbench.renderers.swt.LazyStackRenderer.lambda$0(LazyStackRenderer.java:75)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler.lambda$0(UIEventHandler.java:38)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:236)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:133)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:4561)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:219)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:38)
> at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:205)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:203)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234)
> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:151)
> at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:132)
> at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:75)
> at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:44)
> at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:55)
> at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:63)
> at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:424)
> at org.eclipse.e4.ui.model.application.ui.impl.ElementContainerImpl.setSelectedElementGen(ElementContainerImpl.java:170)
> at org.eclipse.e4.ui.model.application.ui.impl.ElementContainerImpl.setSelectedElement(ElementContainerImpl.java:188)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.showElementInWindow(ModelServiceImpl.java:661)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:625)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.delegateBringToTop(PartServiceImpl.java:790)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.bringToTop(PartServiceImpl.java:404)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1266)
> at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:3195)
> at org.eclipse.ui.internal.WorkbenchPage.lambda$9(WorkbenchPage.java:3100)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:72)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3098)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3068)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3059)
> at org.eclipse.ui.ide.IDE.openEditor(IDE.java:569)
> at org.eclipse.ui.ide.IDE.openEditor(IDE.java:524)
> at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:363)
> at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:170)
> at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:285)
> at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:251)
> at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:274)
> at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:252)
> at org.eclipse.jdt.internal.ui.navigator.OpenAndExpand.run(OpenAndExpand.java:53)
> at org.eclipse.ui.actions.RetargetAction.run(RetargetAction.java:215)
> at org.eclipse.ui.navigator.CommonNavigatorManager$1.open(CommonNavigatorManager.java:183)
> at org.eclipse.ui.OpenAndLinkWithEditorHelper$InternalListener.open(OpenAndLinkWithEditorHelper.java:48)
> at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:802)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
> at org.eclipse.ui.internal.JFaceUtil.lambda$0(JFaceUtil.java:47)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:174)
> at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:799)
> at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1115)
> at org.eclipse.ui.navigator.CommonViewer.handleOpen(CommonViewer.java:454)
> at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:275)
> at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:270)
> at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:310)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4105)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1037)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3922)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3524)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1160)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1049)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:155)
> at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:658)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:557)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:154)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:150)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:401)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:657)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:594)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1447)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years
[JBoss JIRA] (JBIDE-27251) Create an overarching pipeline to build/release all projects in one go
by Jan Richter (Jira)
Jan Richter created JBIDE-27251:
-----------------------------------
Summary: Create an overarching pipeline to build/release all projects in one go
Key: JBIDE-27251
URL: https://issues.redhat.com/browse/JBIDE-27251
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: qa
Reporter: Jan Richter
Assignee: Jan Richter
Fix For: LATER
Once all previous tasks are complete:
Create a pipeline to trigger all the projects' builds in the proper sequence. The pipeline needs to have a release switch:
- off - run all the builds in snapshot mode
- on - run all builds in release mode
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years
[JBoss JIRA] (JBIDE-27250) Integrate RSP snapshots/stable builds into server-connector
by Jan Richter (Jira)
Jan Richter created JBIDE-27250:
-----------------------------------
Summary: Integrate RSP snapshots/stable builds into server-connector
Key: JBIDE-27250
URL: https://issues.redhat.com/browse/JBIDE-27250
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: qa
Reporter: Jan Richter
Assignee: Jan Richter
Fix For: LATER
Once RSP server has proper snapshot & stable builds uploaded:
Adjust the build scripts in vscode-server-connector to use the respective versions of RSP based on the project's status (nightly/release).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years
[JBoss JIRA] (JBIDE-27249) Differentitate between snapshot and stable build in RSP-server
by Jan Richter (Jira)
Jan Richter created JBIDE-27249:
-----------------------------------
Summary: Differentitate between snapshot and stable build in RSP-server
Key: JBIDE-27249
URL: https://issues.redhat.com/browse/JBIDE-27249
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: qa
Reporter: Jan Richter
Assignee: Ondrej Dockal
Fix For: LATER
RSP-server only uses snapshot builds. Add the ability to create a stable release from the build pipeline:
- add a switch to choose whether to run snapshot (default) or release
- on release, promote the build artifacts to a stable location
- add a '-latest' symlink to the upload location pointing to the latest uploaded build
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years
[JBoss JIRA] (JBIDE-27245) StackOverflowException when use module-alias in module.xml config
by MARCOS DONATO (Jira)
[ https://issues.redhat.com/browse/JBIDE-27245?page=com.atlassian.jira.plug... ]
MARCOS DONATO updated JBIDE-27245:
----------------------------------
Attachment: screenshot-1.png
> StackOverflowException when use module-alias in module.xml config
> -----------------------------------------------------------------
>
> Key: JBIDE-27245
> URL: https://issues.redhat.com/browse/JBIDE-27245
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.14.0.Final, 4.15.0.Final
> Reporter: MARCOS DONATO
> Priority: Major
> Attachments: image-2020-04-28-22-08-53-369.png, image-2020-04-28-22-10-26-820.png, image-2020-04-28-22-10-59-398.png, screenshot-1.png
>
>
> When we have a jboss eap 6.4 environment configured with a module in main slot pointing to a target slot via "module-alias" in module.xml ... eclipse workspace fail to startup with an stackoverflowexception message.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years
[JBoss JIRA] (JBIDE-27245) StackOverflowException when use module-alias in module.xml config
by MARCOS DONATO (Jira)
[ https://issues.redhat.com/browse/JBIDE-27245?page=com.atlassian.jira.plug... ]
MARCOS DONATO updated JBIDE-27245:
----------------------------------
Steps to Reproduce:
have an pre-installed jboss eap 6.4
have an pre-installed eclipse IDE (tested with 2020-03)
have installed jboss tools plugin from marketplace (tested with 4.14)
open a workspace
create the server with enviroment pointing to preview jboss installation
start jboss (must run without failure)
stop jboss
close eclipse
add a new module to jboss installation
add two slots to module, one called "main" and another called "alternative"
in "alternative" slot, add resources and depencencies to module.xml
in "main" slot, set module.xml to use module-alias pointing to slot "alternative"
start eclipse (on startup process several errors occurs pointing to StackOverflowException, see eclipse logs)
Edit::
- Create / use an enterprise projetct with an ejb-module, web-module and an ear project.
- Reference jboss module on MANIFES.MF on both (ear / war projects)
If you referer same module on both "MF" files you will get failure. If remove from "war" and restart eclipse, it starts up ok.
Regards
was:
have an pre-installed jboss eap 6.4
have an pre-installed eclipse IDE (tested with 2020-03)
have installed jboss tools plugin from marketplace (tested with 4.14)
open a workspace
create the server with enviroment pointing to preview jboss installation
start jboss (must run without failure)
stop jboss
close eclipse
add a new module to jboss installation
add two slots to module, one called "main" and another called "alternative"
in "alternative" slot, add resources and depencencies to module.xml
in "main" slot, set module.xml to use module-alias pointing to slot "alternative"
start eclipse (on startup process several errors occurs pointing to StackOverflowException, see eclipse logs)
> StackOverflowException when use module-alias in module.xml config
> -----------------------------------------------------------------
>
> Key: JBIDE-27245
> URL: https://issues.redhat.com/browse/JBIDE-27245
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.14.0.Final, 4.15.0.Final
> Reporter: MARCOS DONATO
> Priority: Major
> Attachments: image-2020-04-28-22-08-53-369.png, image-2020-04-28-22-10-26-820.png, image-2020-04-28-22-10-59-398.png
>
>
> When we have a jboss eap 6.4 environment configured with a module in main slot pointing to a target slot via "module-alias" in module.xml ... eclipse workspace fail to startup with an stackoverflowexception message.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years