April 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24551) reactivate Sonarcloud.io updates for jbosstools-server

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24551?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24551: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > reactivate Sonarcloud.io updates for jbosstools-server > ------------------------------------------------------ > > Key: JBIDE-24551 > URL: https://issues.jboss.org/browse/JBIDE-24551 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, server > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Fix For: 4.6.x > > Attachments: screenshot-1.png, screenshot-2.png > > > last update was the 21 February > !screenshot-1.png|thumbnail! > https://sonarcloud.io/dashboard?id=org.jboss.tools%3Aserver.all -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23658) Hibernate console configuration wizard problems - and no way to get specifics

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23658?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23658: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Hibernate console configuration wizard problems - and no way to get specifics > ----------------------------------------------------------------------------- > > Key: JBIDE-23658 > URL: https://issues.jboss.org/browse/JBIDE-23658 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.4.2.Final > Environment: Neon.1 and Neon.2, Windows 7, targeting Oracle > Reporter: Jesper Skov > Assignee: Koen Aers > Fix For: 4.6.x > > Attachments: empty-clean.zip > > > Creating a Hibernate Console Configuration using the wizard fails for most of our projects. > All the feedback we have is the text in red: "Could not create JPA based Configuration" > I would have liked to qualify this problem report with some more information. But there is no problems reported in the eclipse log. > I have tried enabling debugging, as per http://docs.jboss.org/tools/latest/en/hibernatetools/html/plugins.html#de..., without getting any output to the Eclipse Error console, or to the hibernate log file. > We wonder if maybe the plugin/perspective is just dead (or dying). > The plugin documentation has snapshots from 2010/2011, and the JBossTools documentation itself (http://docs.jboss.org/tools/latest/) was not updated since 4.1.0/2013. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22351) ExecutionException in JettyServerRunner.run

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22351?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22351: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > ExecutionException in JettyServerRunner.run > ------------------------------------------- > > Key: JBIDE-22351 > URL: https://issues.jboss.org/browse/JBIDE-22351 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.3.1.Final > Reporter: Automated Error Reporting Bot > Assignee: Xavier Coulon > Fix For: 4.6.x > > > The following problem was reported via the automated error reporting: > Message: Failed to start 'LiveReload-Proxy-Server-50347:80' > {noformat} > org.eclipse.core.commands.ExecutionException: Cannot start LiveReload Server: port 50347 is already in use. > at org.jboss.tools.livereload.core.internal.server.jetty.JettyServerRunner.run(JettyServerRunner.java:128) > at java.lang.Thread.run(Thread.java:745) > {noformat} > Bundles: > | org.jboss.tools.livereload.core | 1.4.0.Alpha1-v20160401-2041-B449 | 1.4.0.Alpha1-v20160401-2041-B449 | > Operating Systems: > | MacOSX | 10.10.5 | 10.10.5 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/572cf35ee4b0a54983...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25606) Maven Formatter Plugin: current formatter causes unnecessary errors

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25606?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25606: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Maven Formatter Plugin: current formatter causes unnecessary errors > ------------------------------------------------------------------- > > Key: JBIDE-25606 > URL: https://issues.jboss.org/browse/JBIDE-25606 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Fix For: 4.6.x > > > Current maven formatter plugin 2.0.1 is using the Eclipse formatter that was in Mars. If will complain even if you format the code in current Eclipse Oxygen. We should use the latest version (2.7.0, 2.7.1 has bugs) and see if it wont complain if when code is formatted in the IDE. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24953) [jst] Code completion fails with Unhandled event loop exception

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24953?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24953: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > [jst] Code completion fails with Unhandled event loop exception > --------------------------------------------------------------- > > Key: JBIDE-24953 > URL: https://issues.jboss.org/browse/JBIDE-24953 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jst > Affects Versions: 4.4.4.Final > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.6.x > > > In BZ 520211, s3lvatico(a)gmail.com reported: > {quote} > What steps will reproduce the problem? > 1. While working on a maven project, define a composite jsf component in another maven project (inside the same workspace) > 2. While authoring a new jsf (xhtml) page, use the newly created component > 3. Activate the code completion feature (CTRL-space) inside the component's tag OR in any other jsf tag. > + jboss tools 4.4.4 > {code} > -- Error Details -- > Date: Wed Jul 26 15:08:46 CEST 2017 > Message: Unhandled event loop exception > Severity: Error > Product: Eclipse 4.6.3.20170314-1500 (org.eclipse.epp.package.jee.product) > Plugin: org.eclipse.ui > Session Data: > eclipse.buildId=4.6.3.M20170301-0400 > java.version=1.8.0_121 > java.vendor=Oracle Corporation > BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US > Framework arguments: -product org.eclipse.epp.package.jee.product > Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.jee.product -data C:\dev\eclipse\jee.neon.3.3\ws0 -clean > Exception Stack Trace: > java.lang.StackOverflowError > at org.eclipse.wst.xml.core.internal.catalog.Catalog$InternalResolver.resolveRewrite(Catalog.java:303) > at org.eclipse.wst.xml.core.internal.catalog.Catalog$InternalResolver.resolveURI(Catalog.java:368) > at org.eclipse.wst.xml.core.internal.catalog.Catalog.resolveURI(Catalog.java:759) > at org.eclipse.wst.xml.core.internal.catalog.Catalog.resolveSubordinateCatalogs(Catalog.java:736) > at org.eclipse.wst.xml.core.internal.catalog.Catalog$InternalResolver.resolveURI(Catalog.java:380) > at org.eclipse.wst.xml.core.internal.catalog.Catalog.resolveURI(Catalog.java:759) > at org.jboss.tools.jst.web.kb.taglib.TagLibraryManager.getStaticTLD(TagLibraryManager.java:92) > at org.jboss.tools.jst.web.kb.internal.StaticLibraries.getLibraries(StaticLibraries.java:44) > at org.jboss.tools.jst.web.kb.internal.KbProject.getTagLibraries(KbProject.java:135) > at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getCompositeLibraries(FaceletTagLibrary.java:90) > at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:128) > at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130) > at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130) > at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130) > at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130) > at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130) > at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130) > at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130) > at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130) > at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130) > at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130) > at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130) > at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130) > at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130) > at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130) > at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130) > at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130) > at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130) > at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130) > at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130) > at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130) > at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130) > at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130) > at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130) > at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130) > [... the stack trace goes on and on...]{code}{quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20742) jboss-kitchensink-angularjs project has error after imported from JBoss Central

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20742?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20742: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > jboss-kitchensink-angularjs project has error after imported from JBoss Central > ------------------------------------------------------------------------------- > > Key: JBIDE-20742 > URL: https://issues.jboss.org/browse/JBIDE-20742 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, upstream > Affects Versions: 4.3.0.CR1 > Environment: JBDS 9.0.0.CR1-v20150918-0257-B105 with bundled EAP > Reporter: Vlado Pakan > Assignee: Victor Rubezhny > Labels: regression > Fix For: 4.6.x > > Attachments: angularjserror.png > > > 1. Install AngularJS from JBoss Central Early access > 2. Import jboss-kitchensink-angularjs from JBoss Central > ERROR: > !angularjserror.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22933) SWTException below VpvEditorPart.setFocus (thrown in Widget.checkWidget)

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22933?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22933: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > SWTException below VpvEditorPart.setFocus (thrown in Widget.checkWidget) > ------------------------------------------------------------------------ > > Key: JBIDE-22933 > URL: https://issues.jboss.org/browse/JBIDE-22933 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Reporter: Automated Error Reporting Bot > Assignee: Ilya Buziuk > Fix For: 4.6.x > > > The following problem was reported via the automated error reporting: > Message: Error setting focus to : org.eclipse.e4.ui.model.application.ui.basic.impl.PartImpl index.html > {noformat} > org.eclipse.swt.SWTException: Widget is disposed > at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:420) > at org.eclipse.swt.widgets.Control.getVisible(Control.java:3116) > at org.eclipse.swt.widgets.Composite.setFocus(Composite.java:1513) > at org.eclipse.swt.widgets.Composite.setFocus(Composite.java:1513) > at org.eclipse.ui.texteditor.StatusTextEditor.setFocus(StatusTextEditor.java:118) > at org.jboss.tools.vpe.preview.editor.VpvEditorPart.setFocus(VpvEditorPart.java:653) > at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPMultiPageEditorPart.setFocus(JSPMultiPageEditorPart.java:186) > at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPMultiPageEditorPart.setFocus(JSPMultiPageEditorPart.java:171) > at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.delegateSetFocus(CompatibilityPart.java:204) > at sun.reflect.GeneratedMethodAccessor.invoke(null:-1) > 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:54) > {noformat} > Bundles: > | org.eclipse.e4.core.di | 1.6.0.v20160319-0612 | 1.6.0.v20160319-0612 | > | org.eclipse.swt | 3.105.0.v20160603-0902 | 3.105.0.v20160603-0902 | > | org.eclipse.ui | 3.108.0.v20160518-1929 | 3.108.0.v20160518-1929 | > | org.jboss.tools.jst.web.ui | 3.8.0.Final-v20160609-2146-B2 | 3.8.0.Final-v20160609-2146-B2 | > | org.jboss.tools.vpe.preview.editor | 3.8.0.Final-v20160609-2229-B3 | 3.8.0.Final-v20160609-2229-B3 | > Operating Systems: > | Linux | 4.5.7.fc23 | 4.5.7.fc23 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5774bdbce4b03c6ed0...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22964) Fuse examples are found even though Fuse is not installed (and is not available in Central)

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22964?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22964: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Fuse examples are found even though Fuse is not installed (and is not available in Central) > ------------------------------------------------------------------------------------------- > > Key: JBIDE-22964 > URL: https://issues.jboss.org/browse/JBIDE-22964 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.4.1.AM3 > Environment: Devstudio 10.1.0.AM3-v20160809-0722-B5729 > Reporter: Radim Hopp > Fix For: 4.6.x > > > After turning Early Access on, camel, fuse, brms examples can be looked up in Central even though Integration stack is not on the Software/Update page. > That is probably because _jboss.discovery.site.integration-stack.url_ and _jboss.discovery.earlyaccess.site.integration-stack.url_ properties are configured in ide-config.properties. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19032) CordovaSim: Need to substitute 'Start Page' with the 'Start Page Parameters' in the launch config

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19032?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-19032: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > CordovaSim: Need to substitute 'Start Page' with the 'Start Page Parameters' in the launch config > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-19032 > URL: https://issues.jboss.org/browse/JBIDE-19032 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cordovasim > Affects Versions: 4.2.1.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.6.x > > > see the following [comment|https://issues.jboss.org/browse/JBIDE-18900?focusedCommentId=1303...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22937) 3rd party caused XPCOMException below VpeCopyCreator.addAttributes

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22937?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22937: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > 3rd party caused XPCOMException below VpeCopyCreator.addAttributes > ------------------------------------------------------------------ > > Key: JBIDE-22937 > URL: https://issues.jboss.org/browse/JBIDE-22937 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Reporter: Automated Error Reporting Bot > Assignee: Ilya Buziuk > Fix For: 4.6.x > > > The following problem was reported via the automated error reporting: > Message: The function "setAttribute" returned an error condition (0x80530005) > {noformat} > org.mozilla.xpcom.XPCOMException: The function "setAttribute" returned an error condition (0x80530005) > at EXTERNAL.EXTERNAL(null:-1) > at com.sun.proxy.$Proxy.setAttribute(null:-1) > at org.jboss.tools.vpe.editor.template.VpeCopyCreator.addAttributes(VpeCopyCreator.java:150) > at org.jboss.tools.vpe.editor.template.VpeCopyCreator.create(VpeCopyCreator.java:96) > at org.jboss.tools.vpe.editor.template.VpeHtmlTemplate.createVisualElement(VpeHtmlTemplate.java:209) > at org.jboss.tools.vpe.editor.template.VpeHtmlTemplate.create(VpeHtmlTemplate.java:158) > at org.jboss.tools.vpe.editor.template.VpeTemplateSafeWrapper.create(VpeTemplateSafeWrapper.java:73) > at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:372) > at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) > at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:543) > at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:476) > at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) > at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:543) > at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:476) > at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) > at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:543) > at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:476) > at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) > at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:543) > at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:476) > at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) > at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:543) > at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:476) > at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) > at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:543) > at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:476) > at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) > at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:543) > at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:476) > at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) > at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:543) > at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:476) > at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) > at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:543) > at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:476) > at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) > at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:543) > at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:476) > at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) > at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:543) > at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:476) > at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) > at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.buildDom(VpeVisualDomBuilder.java:192) > at org.jboss.tools.vpe.editor.VpeController.init(VpeController.java:306) > at org.jboss.tools.vpe.editor.VpeEditorPart$17.load(VpeEditorPart.java:808) > at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.onLoadWindow(MozillaEditor.java:810) > at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.access$18(MozillaEditor.java:806) > at org.jboss.tools.vpe.editor.mozilla.MozillaEditor$14.completed(MozillaEditor.java:604) > at org.eclipse.swt.browser.Mozilla$23.run(Mozilla.java:4186) > at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:186) > at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:145) > at org.eclipse.swt.widgets.Display.syncExec(Display.java:4761) > at org.eclipse.swt.browser.Mozilla.OnStateChange(Mozilla.java:4193) > at org.eclipse.swt.browser.Mozilla$9.method3(Mozilla.java:1109) > at org.eclipse.swt.internal.mozilla.XPCOMObject.callback3(XPCOMObject.java:271) > at org.eclipse.swt.internal.win32.OS.DispatchMessageW(OS.java:-2) > at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2549) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3767) > {noformat} > Bundles: > | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.104.2.v20160212-1350 | > | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20150507-1945 | > | org.jboss.tools.jst.web.ui | 3.7.1.Final-v20160331-0256-B96 | 3.7.1.Final-v20160331-0256-B96 | > | org.jboss.tools.vpe | 3.7.1.Final-v20160331-0327-B91 | 3.7.1.Final-v20160331-0327-B91 | > | org.jboss.tools.vpe.xulrunner | 3.7.1.Final-v20160331-0327-B91 | 3.7.1.Final-v20160331-0327-B91 | > Operating Systems: > | Windows | 6.1.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/574d610ce4b06056d2...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2018