jbosstools-issues April 2019

jbosstools-issues@lists.jboss.org

1 participants
296 discussions

[JBoss JIRA] (JBIDE-26606) For JBIDE 4.12.0.AM1: Prepare for 4.12.0.AM1 / 12.12.0.AM1 [central]

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26606?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-26606: ---------------------------------- Assignee: Jeff MAURY > For JBIDE 4.12.0.AM1: Prepare for 4.12.0.AM1 / 12.12.0.AM1 [central] > -------------------------------------------------------------------- > > Key: JBIDE-26606 > URL: https://issues.jboss.org/browse/JBIDE-26606 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.12.0.AM1 > > > For JBIDE 4.12.0.AM1 [central]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.12.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.12.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.12.0.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.11.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.11.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26605) For JBIDE 4.12.0.AM1: Prepare for 4.12.0.AM1 / 12.12.0.AM1 [foundation]

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26605?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-26605: ---------------------------------- Assignee: Rob Stryker > For JBIDE 4.12.0.AM1: Prepare for 4.12.0.AM1 / 12.12.0.AM1 [foundation] > ----------------------------------------------------------------------- > > Key: JBIDE-26605 > URL: https://issues.jboss.org/browse/JBIDE-26605 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: foundation > Reporter: Jeff MAURY > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.12.0.AM1 > > > For JBIDE 4.12.0.AM1 [foundation]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.12.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.12.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.12.0.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.11.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.11.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for foundation task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26605) For JBIDE 4.12.0.AM1: Prepare for 4.12.0.AM1 / 12.12.0.AM1 [foundation]

by Jeff MAURY (Jira)

Jeff MAURY created JBIDE-26605: ---------------------------------- Summary: For JBIDE 4.12.0.AM1: Prepare for 4.12.0.AM1 / 12.12.0.AM1 [foundation] Key: JBIDE-26605 URL: https://issues.jboss.org/browse/JBIDE-26605 Project: Tools (JBoss Tools) Issue Type: Task Components: foundation Reporter: Jeff MAURY Fix For: 4.12.0.AM1 For JBIDE 4.12.0.AM1 [foundation]: Please perform the following tasks: 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.12.0.AM1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.12.0.AM1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.12.0.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.11.0.Final-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.11.0.Final-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for foundation task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26598) Unable to connect to "local" JMX process when instance launched with JDK 11

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26598?page=com.atlassian.jira.plugi... ] Josef Kopriva reassigned JBIDE-26598: ------------------------------------- Assignee: Ondrej Dockal > Unable to connect to "local" JMX process when instance launched with JDK 11 > --------------------------------------------------------------------------- > > Key: JBIDE-26598 > URL: https://issues.jboss.org/browse/JBIDE-26598 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.11.0.Final > Reporter: Aurélien Pupier > Assignee: Ondrej Dockal > Priority: Blocker > Fix For: 4.11.0.Final > > > {code} > org.jboss.tools.jmx.local > Error > Wed Mar 27 09:25:29 CET 2019 > Unable to connect to jvm > org.jboss.tools.jmx.jvmmonitor.core.JvmCoreException: Could not get JMX service URL (PID: 9470) > at org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.initialize(ActiveJvm.java:462) > at org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.initialize(ActiveJvm.java:445) > at org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.connect(ActiveJvm.java:233) > at org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.connect(ActiveJvm.java:213) > at org.jboss.tools.jmx.local.internal.JvmConnectionWrapper.connect(JvmConnectionWrapper.java:118) > at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4768) org.eclipse.debug.ui.toggleBreakpointsTargetFactory extension failed to load breakpoint toggle target because the specified id is already registered. Specified ID is: org.chromium.debug.ui.ChromiumToggleBreakpointTargetFactory

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBDS-4768?page=com.atlassian.jira.plugin.... ] Ondrej Dockal updated JBDS-4768: -------------------------------- Description: {code} eclipse.buildId=4.11.0.I20190307-0500 java.version=11.0.2 java.vendor=Oracle Corporation BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -data file:/home/odockal/eclipse-workspace-jbt411-central/ -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product org.eclipse.debug.ui Error Fri Mar 29 16:03:31 CET 2019 org.eclipse.debug.ui.toggleBreakpointsTargetFactory extension failed to load breakpoint toggle target because the specified id is already registered. Specified ID is: org.chromium.debug.ui.ChromiumToggleBreakpointTargetFactory eclipse.buildId=4.11.0.I20190307-0500 java.version=11.0.2 java.vendor=Oracle Corporation BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -data file:/home/odockal/eclipse-workspace-jbt411-central/ -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product {code} And randomly occurring error, happened while testing installer component: {code} org.eclipse.ui Error Fri Mar 29 16:17:03 CET 2019 Unhandled event loop exception org.eclipse.swt.SWTException: Widget is disposed at org.eclipse.swt.SWT.error(SWT.java:4699) at org.eclipse.swt.SWT.error(SWT.java:4614) at org.eclipse.swt.SWT.error(SWT.java:4585) at org.eclipse.swt.widgets.Widget.error(Widget.java:530) at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:467) at org.eclipse.swt.widgets.Composite.getChildren(Composite.java:736) at org.eclipse.epp.internal.mpc.ui.wizards.MarketplaceDropAdapter.lambda$0(MarketplaceDropAdapter.java:136) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:40) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:185) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:5026) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4582) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1173) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1062) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:155) at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:644) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:566) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:155) 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:400) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:661) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:597) at org.eclipse.equinox.launcher.Main.run(Main.java:1476) at org.eclipse.equinox.launcher.Main.main(Main.java:1449) {code} was: {code} eclipse.buildId=4.11.0.I20190307-0500 java.version=11.0.2 java.vendor=Oracle Corporation BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -data file:/home/odockal/eclipse-workspace-jbt411-central/ -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product org.eclipse.debug.ui Error Fri Mar 29 16:03:31 CET 2019 org.eclipse.debug.ui.toggleBreakpointsTargetFactory extension failed to load breakpoint toggle target because the specified id is already registered. Specified ID is: org.chromium.debug.ui.ChromiumToggleBreakpointTargetFactory eclipse.buildId=4.11.0.I20190307-0500 java.version=11.0.2 java.vendor=Oracle Corporation BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -data file:/home/odockal/eclipse-workspace-jbt411-central/ -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product org.eclipse.ui Error Fri Mar 29 16:17:03 CET 2019 Unhandled event loop exception org.eclipse.swt.SWTException: Widget is disposed at org.eclipse.swt.SWT.error(SWT.java:4699) at org.eclipse.swt.SWT.error(SWT.java:4614) at org.eclipse.swt.SWT.error(SWT.java:4585) at org.eclipse.swt.widgets.Widget.error(Widget.java:530) at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:467) at org.eclipse.swt.widgets.Composite.getChildren(Composite.java:736) at org.eclipse.epp.internal.mpc.ui.wizards.MarketplaceDropAdapter.lambda$0(MarketplaceDropAdapter.java:136) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:40) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:185) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:5026) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4582) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1173) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1062) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:155) at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:644) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:566) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:155) 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:400) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:661) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:597) at org.eclipse.equinox.launcher.Main.run(Main.java:1476) at org.eclipse.equinox.launcher.Main.main(Main.java:1449) {code} > org.eclipse.debug.ui.toggleBreakpointsTargetFactory extension failed to load breakpoint toggle target because the specified id is already registered. Specified ID is: org.chromium.debug.ui.ChromiumToggleBreakpointTargetFactory > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-4768 > URL: https://issues.jboss.org/browse/JBDS-4768 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Bug > Components: central-update, updatesite > Affects Versions: 12.11.0.GA > Environment: Fedora 29, openjdk 11 > Reporter: Ondrej Dockal > Assignee: Jeff MAURY > Priority: Major > Fix For: 12.x > > > {code} > eclipse.buildId=4.11.0.I20190307-0500 > java.version=11.0.2 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product org.eclipse.epp.package.jee.product > Command-line arguments: -data file:/home/odockal/eclipse-workspace-jbt411-central/ -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product > org.eclipse.debug.ui > Error > Fri Mar 29 16:03:31 CET 2019 > org.eclipse.debug.ui.toggleBreakpointsTargetFactory extension failed to load breakpoint toggle target because the specified id is already registered. Specified ID is: org.chromium.debug.ui.ChromiumToggleBreakpointTargetFactory > eclipse.buildId=4.11.0.I20190307-0500 > java.version=11.0.2 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product org.eclipse.epp.package.jee.product > Command-line arguments: -data file:/home/odockal/eclipse-workspace-jbt411-central/ -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product > {code} > And randomly occurring error, happened while testing installer component: > {code} > org.eclipse.ui > Error > Fri Mar 29 16:17:03 CET 2019 > Unhandled event loop exception > org.eclipse.swt.SWTException: Widget is disposed > at org.eclipse.swt.SWT.error(SWT.java:4699) > at org.eclipse.swt.SWT.error(SWT.java:4614) > at org.eclipse.swt.SWT.error(SWT.java:4585) > at org.eclipse.swt.widgets.Widget.error(Widget.java:530) > at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:467) > at org.eclipse.swt.widgets.Composite.getChildren(Composite.java:736) > at org.eclipse.epp.internal.mpc.ui.wizards.MarketplaceDropAdapter.lambda$0(MarketplaceDropAdapter.java:136) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:40) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:185) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:5026) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4582) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1173) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1062) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:155) > at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:644) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:566) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:155) > 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:400) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:661) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:597) > at org.eclipse.equinox.launcher.Main.run(Main.java:1476) > at org.eclipse.equinox.launcher.Main.main(Main.java:1449) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBDS-4768?page=com.atlassian.jira.plugin.... ] Ondrej Dockal commented on JBDS-4768: ------------------------------------- [~jeffmaury] I found it, it has been reported already some time ago, has not been really solved nor any workaround exists, yet, does not seem like anything critical cause nobody bothers to take a deep look. > org.eclipse.debug.ui.toggleBreakpointsTargetFactory extension failed to load breakpoint toggle target because the specified id is already registered. Specified ID is: org.chromium.debug.ui.ChromiumToggleBreakpointTargetFactory > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-4768 > URL: https://issues.jboss.org/browse/JBDS-4768 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Bug > Components: central-update, updatesite > Affects Versions: 12.11.0.GA > Environment: Fedora 29, openjdk 11 > Reporter: Ondrej Dockal > Assignee: Jeff MAURY > Priority: Major > Fix For: 12.x > > > {code} > eclipse.buildId=4.11.0.I20190307-0500 > java.version=11.0.2 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product org.eclipse.epp.package.jee.product > Command-line arguments: -data file:/home/odockal/eclipse-workspace-jbt411-central/ -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product > org.eclipse.debug.ui > Error > Fri Mar 29 16:03:31 CET 2019 > org.eclipse.debug.ui.toggleBreakpointsTargetFactory extension failed to load breakpoint toggle target because the specified id is already registered. Specified ID is: org.chromium.debug.ui.ChromiumToggleBreakpointTargetFactory > eclipse.buildId=4.11.0.I20190307-0500 > java.version=11.0.2 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product org.eclipse.epp.package.jee.product > Command-line arguments: -data file:/home/odockal/eclipse-workspace-jbt411-central/ -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product > org.eclipse.ui > Error > Fri Mar 29 16:17:03 CET 2019 > Unhandled event loop exception > org.eclipse.swt.SWTException: Widget is disposed > at org.eclipse.swt.SWT.error(SWT.java:4699) > at org.eclipse.swt.SWT.error(SWT.java:4614) > at org.eclipse.swt.SWT.error(SWT.java:4585) > at org.eclipse.swt.widgets.Widget.error(Widget.java:530) > at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:467) > at org.eclipse.swt.widgets.Composite.getChildren(Composite.java:736) > at org.eclipse.epp.internal.mpc.ui.wizards.MarketplaceDropAdapter.lambda$0(MarketplaceDropAdapter.java:136) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:40) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:185) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:5026) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4582) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1173) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1062) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:155) > at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:644) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:566) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:155) > 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:400) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:661) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:597) > at org.eclipse.equinox.launcher.Main.run(Main.java:1476) > at org.eclipse.equinox.launcher.Main.main(Main.java:1449) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

← Newer
1
...
27
28
29
30
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2019