May 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26007) Fuse Tools New and Noteworthy for 4.6.0.AM2

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26007?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26007: ------------------------------- Labels: task (was: ) > Fuse Tools New and Noteworthy for 4.6.0.AM2 > --------------------------------------------------- > > Key: JBIDE-26007 > URL: https://issues.jboss.org/browse/JBIDE-26007 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: fusetools, fusetools-extras > Reporter: Jeff MAURY > Assignee: Lars Heinemann > Priority: Critical > Labels: task > Fix For: 4.6.0.AM2 > > > Lars Heinemann, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Fuse Tools JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Fuse Tools, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Fuse Tools by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-25999 #comment Create N&N for Fuse Tools 4.6.0.AM2 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Fuse Tools for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26008) Maven New and Noteworthy for 4.6.0.AM2

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-26008: ---------------------------------- Summary: Maven New and Noteworthy for 4.6.0.AM2 Key: JBIDE-26008 URL: https://issues.jboss.org/browse/JBIDE-26008 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: maven Reporter: Jeff MAURY Priority: Critical Fix For: 4.6.0.AM2 Jeff MAURY, Search for your component's New and Noteworthy issues: Queries: * [Completed Maven JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] If no N&N issues are found for Maven, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. Document the ones relevant for Maven by submitting a pull request against: * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... If your PR's commit comment is of the form... {code}JBIDE-25999 #comment Create N&N for Maven 4.6.0.AM2 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. If there is nothing new or noteworthy for Maven for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26008) Maven New and Noteworthy for 4.6.0.AM2

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26008?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-26008: ---------------------------------- Assignee: Jeff MAURY > Maven New and Noteworthy for 4.6.0.AM2 > --------------------------------------------------- > > Key: JBIDE-26008 > URL: https://issues.jboss.org/browse/JBIDE-26008 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: maven > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.6.0.AM2 > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Maven JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Maven, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Maven by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-25999 #comment Create N&N for Maven 4.6.0.AM2 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Maven for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26008) Maven New and Noteworthy for 4.6.0.AM2

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26008?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26008: ------------------------------- Labels: task (was: ) > Maven New and Noteworthy for 4.6.0.AM2 > --------------------------------------------------- > > Key: JBIDE-26008 > URL: https://issues.jboss.org/browse/JBIDE-26008 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: maven > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.6.0.AM2 > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Maven JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Maven, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Maven by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-25999 #comment Create N&N for Maven 4.6.0.AM2 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Maven for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26009) Batch New and Noteworthy for 4.6.0.AM2

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-26009: ---------------------------------- Summary: Batch New and Noteworthy for 4.6.0.AM2 Key: JBIDE-26009 URL: https://issues.jboss.org/browse/JBIDE-26009 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: batch Reporter: Jeff MAURY Priority: Critical Fix For: 4.6.0.AM2 Jeff MAURY, Search for your component's New and Noteworthy issues: Queries: * [Completed Batch JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] If no N&N issues are found for Batch, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. Document the ones relevant for Batch by submitting a pull request against: * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... If your PR's commit comment is of the form... {code}JBIDE-25999 #comment Create N&N for Batch 4.6.0.AM2 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. If there is nothing new or noteworthy for Batch for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26009) Batch New and Noteworthy for 4.6.0.AM2

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26009?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-26009: ---------------------------------- Assignee: Jeff MAURY > Batch New and Noteworthy for 4.6.0.AM2 > --------------------------------------------------- > > Key: JBIDE-26009 > URL: https://issues.jboss.org/browse/JBIDE-26009 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: batch > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.6.0.AM2 > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Batch JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Batch, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Batch by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-25999 #comment Create N&N for Batch 4.6.0.AM2 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Batch for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26009) Batch New and Noteworthy for 4.6.0.AM2

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26009?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26009: ------------------------------- Labels: task (was: ) > Batch New and Noteworthy for 4.6.0.AM2 > --------------------------------------------------- > > Key: JBIDE-26009 > URL: https://issues.jboss.org/browse/JBIDE-26009 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: batch > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.6.0.AM2 > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Batch JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Batch, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Batch by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-25999 #comment Create N&N for Batch 4.6.0.AM2 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Batch for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26010) Server New and Noteworthy for 4.6.0.AM2

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-26010: ---------------------------------- Summary: Server New and Noteworthy for 4.6.0.AM2 Key: JBIDE-26010 URL: https://issues.jboss.org/browse/JBIDE-26010 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: server, jmx, archives Reporter: Jeff MAURY Priority: Critical Fix For: 4.6.0.AM2 Rob Stryker, Search for your component's New and Noteworthy issues: Queries: * [Completed Server JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] If no N&N issues are found for Server, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. Document the ones relevant for Server by submitting a pull request against: * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... If your PR's commit comment is of the form... {code}JBIDE-25999 #comment Create N&N for Server 4.6.0.AM2 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. If there is nothing new or noteworthy for Server for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26010) Server New and Noteworthy for 4.6.0.AM2

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26010?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-26010: ---------------------------------- Assignee: Rob Stryker > Server New and Noteworthy for 4.6.0.AM2 > --------------------------------------------------- > > Key: JBIDE-26010 > URL: https://issues.jboss.org/browse/JBIDE-26010 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: archives, jmx, server > Reporter: Jeff MAURY > Assignee: Rob Stryker > Priority: Critical > Labels: task > Fix For: 4.6.0.AM2 > > > Rob Stryker, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Server JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Server, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Server by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-25999 #comment Create N&N for Server 4.6.0.AM2 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Server for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4700) JBoss Developer Studio Fuse Tooling doesn't render graphical editor for camel files

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4700?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4700: ---------------------------------- [~lufimtse] any comments on this? Is Photon any better? Or Fedora 28? Or Fedora 29 (target release 2018-10-23 or 30) ? > JBoss Developer Studio Fuse Tooling doesn't render graphical editor for camel files > ------------------------------------------------------------------------------------ > > Key: JBDS-4700 > URL: https://issues.jboss.org/browse/JBDS-4700 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: fusetools, integration, upstream > Affects Versions: 10.4.0.GA, 11.2.0.GA, 11.3.0.GA > Environment: * Red Hat JBoss Developer Studio 11.3.0.GA, 11.2.0.GA, 10.4.0.GA > * Fuse Tooling plugin versions: 10.3.0.v20180316-1454, 10.2.0.v20180117-1512 > * Fedora 27 > Reporter: Roger Hui > Assignee: Nick Boldt > Fix For: 12.0.0.AM1 > > > JBoss Developer Studio Fuse Tooling doesn't render graphical editor for camel files > {code:title=error log} > org.eclipse.swt.SWTError: No more handles > at org.eclipse.swt.SWT.error(SWT.java:4559) > at org.eclipse.swt.SWT.error(SWT.java:4448) > at org.eclipse.swt.SWT.error(SWT.java:4419) > at org.eclipse.swt.graphics.Cursor.<init>(Cursor.java:180) > at org.eclipse.draw2d.Cursors.<clinit>(Cursors.java:195) > at org.eclipse.gef.ui.palette.FlyoutPaletteComposite$ButtonCanvas.init(FlyoutPaletteComposite.java:1214) > at org.eclipse.gef.ui.palette.FlyoutPaletteComposite$ButtonCanvas.<init>(FlyoutPaletteComposite.java:1180) > at org.eclipse.gef.ui.palette.FlyoutPaletteComposite.createFlyoutControlButton(FlyoutPaletteComposite.java:265) > at org.eclipse.gef.ui.palette.FlyoutPaletteComposite.access$4(FlyoutPaletteComposite.java:264) > at org.eclipse.gef.ui.palette.FlyoutPaletteComposite$Sash.<init>(FlyoutPaletteComposite.java:745) > at org.eclipse.gef.ui.palette.FlyoutPaletteComposite.createSash(FlyoutPaletteComposite.java:291) > at org.eclipse.gef.ui.palette.FlyoutPaletteComposite.<init>(FlyoutPaletteComposite.java:197) > at org.fusesource.ide.camel.editor.internal.CamelDesignEditorFlyoutPaletteComposite.<init>(CamelDesignEditorFlyoutPaletteComposite.java:188) > at org.fusesource.ide.camel.editor.CamelDesignEditor.createPaletteComposite(CamelDesignEditor.java:277) > at org.eclipse.gef.ui.parts.GraphicalEditorWithFlyoutPalette.createPartControl(GraphicalEditorWithFlyoutPalette.java:73) > at org.eclipse.graphiti.ui.editor.DiagramEditor.createPartControl(DiagramEditor.java:320) > at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:241) > at org.fusesource.ide.camel.editor.CamelEditor.createDesignPage(CamelEditor.java:317) > at org.fusesource.ide.camel.editor.CamelEditor.createPages(CamelEditor.java:221) > 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:992) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:661) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:767) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:738) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:732) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:716) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl$1.handleEvent(PartServiceImpl.java:104) > 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:5535) > 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:769) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.bringToTop(PartServiceImpl.java:401) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1188) > 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:3107) > at org.eclipse.ui.ide.IDE.openEditor(IDE.java:563) > at org.eclipse.ui.ide.IDE.openEditor(IDE.java:518) > at org.fusesource.ide.branding.wizards.NewCamelXmlWizard$2.run(NewCamelXmlWizard.java:172) > 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:4577) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4186) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:165) > at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:369) > at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:980) > at org.fusesource.ide.branding.wizards.NewCamelXmlWizard.performFinish(NewCamelXmlWizard.java:109) > at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:778) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:417) > at org.eclipse.jface.dialogs.Dialog.lambda$0(Dialog.java:619) > at org.eclipse.swt.events.SelectionListener$1.widgetSelected(SelectionListener.java:81) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5348) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1348) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4602) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4183) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:818) > at org.eclipse.jface.window.Window.open(Window.java:794) > at org.eclipse.ui.internal.navigator.wizards.WizardShortcutAction.run(WizardShortcutAction.java:99) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:473) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565) > at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5348) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1348) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4602) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4183) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039) > 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, 2 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 May 2018