October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-438) Nullpointer in JavaScript Development Tools Chromium/V8 Remote Debugger: BreakpointAdapterFactory [EBZ#496914]

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/ERT-438?page=com.atlassian.jira.plugin.sy... ] Victor Rubezhny reassigned ERT-438: ----------------------------------- Assignee: Victor Rubezhny > Nullpointer in JavaScript Development Tools Chromium/V8 Remote Debugger: BreakpointAdapterFactory [EBZ#496914] > -------------------------------------------------------------------------------------------------------------- > > Key: ERT-438 > URL: https://issues.jboss.org/browse/ERT-438 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Labels: 3.9, Debug, bzira > Fix For: Oxygen (4.7) > > > Fresh installation of Eclipse Neon for Java EE Developers (contains the plugin 'JavaScript Development Tools Chromium/V8 Remote Debugger'). > Installed ResourceBundle Editor V1.0.5 via Eclipse marketplace. > A Nullpointer occurs when opening any ResourceBundle file with ResourceBundle Editor. Stacktrace see end of post. After deinstalling the Chromium Debugger plugin, the nullpointer is not reproducable anymore and ResourceBundle Editor is working again. > NPE probably caused by empty editorinput? > IResource resource = (IResource) editorPart.getEditorInput().getAdapter(IResource.class); > java.lang.NullPointerException > at org.eclipse.wst.jsdt.chromium.debug.core.model.BreakpointAdapterFactory.getAdapter(BreakpointAdapterFactory.java:25) > at org.eclipse.core.internal.adapter.AdapterFactoryProxy.getAdapter(AdapterFactoryProxy.java:82) > at org.eclipse.core.internal.runtime.AdapterManager.getAdapter(AdapterManager.java:294) > at org.eclipse.ui.part.WorkbenchPart.getAdapter(WorkbenchPart.java:143) > at org.eclipse.ui.texteditor.AbstractTextEditor.getAdapter(AbstractTextEditor.java:6185) > at com.essiembre.eclipse.rbe.ui.editor.i18n.I18nPageEditor.getAdapter(I18nPageEditor.java:90) > at org.eclipse.core.runtime.Adapters.adapt(Adapters.java:59) > at org.eclipse.core.runtime.Adapters.adapt(Adapters.java:100) > at org.eclipse.ui.part.MultiPageEditorPart.getAdapter(MultiPageEditorPart.java:1199) > at com.essiembre.eclipse.rbe.ui.editor.ResourceBundleEditor.getAdapter(ResourceBundleEditor.java:208) > at org.eclipse.debug.internal.ui.actions.ToggleBreakpointsTargetManager$ToggleBreakpointsTargetAdapterFactory.canGetToggleBreakpointsTarget(ToggleBreakpointsTargetManager.java:318) > at org.eclipse.debug.internal.ui.actions.ToggleBreakpointsTargetManager$ToggleBreakpointsTargetAdapterFactory.isEnabled(ToggleBreakpointsTargetManager.java:361) > at org.eclipse.debug.internal.ui.actions.ToggleBreakpointsTargetManager.getEnabledFactories(ToggleBreakpointsTargetManager.java:502) > at org.eclipse.debug.internal.ui.actions.ToggleBreakpointsTargetManager.getPreferredToggleBreakpointsTargetID(ToggleBreakpointsTargetManager.java:542) > at org.eclipse.debug.internal.ui.actions.ToggleBreakpointsTargetManager.getToggleBreakpointsTarget(ToggleBreakpointsTargetManager.java:549) > at org.eclipse.debug.internal.ui.actions.breakpoints.RetargetBreakpointAction.getAdapter(RetargetBreakpointAction.java:49) > at org.eclipse.debug.internal.ui.actions.RetargetAction.partActivated(RetargetAction.java:169) > at org.eclipse.ui.internal.PartService$1.run(PartService.java:84) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.PartService.partActivated(PartService.java:81) > at org.eclipse.ui.internal.WorkbenchWindow$WWinPartService.partActivated(WorkbenchWindow.java:3002) > at org.eclipse.ui.internal.WorkbenchPage$14.run(WorkbenchPage.java:4977) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.WorkbenchPage.firePartActivated(WorkbenchPage.java:4974) > at org.eclipse.ui.internal.WorkbenchPage.access$19(WorkbenchPage.java:4962) > at org.eclipse.ui.internal.WorkbenchPage$E4PartListener.partActivated(WorkbenchPage.java:210) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl$3.run(PartServiceImpl.java:250) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.firePartActivated(PartServiceImpl.java:247) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:757) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:682) > at org.eclipse.e4.ui.internal.workbench.swt.AbstractPartRenderer.activate(AbstractPartRenderer.java:95) > at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer$4.handleEvent(StackRenderer.java:1077) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1366) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1349) > at org.eclipse.swt.widgets.Shell.setActiveControl(Shell.java:1817) > at org.eclipse.swt.widgets.Control.gtk_button_press_event(Control.java:3215) > at org.eclipse.swt.widgets.Control.gtk_button_press_event(Control.java:3151) > at org.eclipse.swt.widgets.Composite.gtk_button_press_event(Composite.java:750) > at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1979) > at org.eclipse.swt.widgets.Control.windowProc(Control.java:5819) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5490) > at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method) > at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:9545) > at org.eclipse.swt.widgets.Display.eventProc(Display.java:1275) > at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method) > at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2495) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4141) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > 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:673) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610) > at org.eclipse.equinox.launcher.Main.run(Main.java:1519) > at org.eclipse.equinox.launcher.Main.main(Main.java:1492) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23399) clean up email generation to avoid invalid addresses

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23399?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23399: ------------------------------- Fix Version/s: 4.4.2.AM3 > clean up email generation to avoid invalid addresses > ---------------------------------------------------- > > Key: JBIDE-23399 > URL: https://issues.jboss.org/browse/JBIDE-23399 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM3 > > > Last batch of notification emails re: JBT 4.4.2.AM2 release (and the previous ones for staging too) all had these recipients: > {code} > -nboldt(a)redhat.com, > Boldt(a)redhat.com, > -fNick(a)redhat.com, > --(a)redhat.com, > -c(a)redhat.com{code} > Seems like a problem with quotes / commandline. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23399) clean up email generation to avoid invalid addresses

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23399?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-23399: ---------------------------------- Assignee: Nick Boldt > clean up email generation to avoid invalid addresses > ---------------------------------------------------- > > Key: JBIDE-23399 > URL: https://issues.jboss.org/browse/JBIDE-23399 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM3 > > > Last batch of notification emails re: JBT 4.4.2.AM2 release (and the previous ones for staging too) all had these recipients: > {code} > -nboldt(a)redhat.com, > Boldt(a)redhat.com, > -fNick(a)redhat.com, > --(a)redhat.com, > -c(a)redhat.com{code} > Seems like a problem with quotes / commandline. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23399) clean up email generation to avoid invalid addresses

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-23399: ---------------------------------- Summary: clean up email generation to avoid invalid addresses Key: JBIDE-23399 URL: https://issues.jboss.org/browse/JBIDE-23399 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Reporter: Nick Boldt Last batch of notification emails re: JBT 4.4.2.AM2 release (and the previous ones for staging too) all had these recipients: {code} -nboldt(a)redhat.com, Boldt(a)redhat.com, -fNick(a)redhat.com, --(a)redhat.com, -c(a)redhat.com{code} Seems like a problem with quotes / commandline. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23388) add checks for jbosstools src zip+sha and browsersim-standalone.zip+sha

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23388?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23388: ------------------------------- Fix Version/s: 4.4.2.AM2 > add checks for jbosstools src zip+sha and browsersim-standalone.zip+sha > ----------------------------------------------------------------------- > > Key: JBIDE-23388 > URL: https://issues.jboss.org/browse/JBIDE-23388 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.2.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM2 > > > When releasing AM2, 4 files were not checked and therefore were not published. > * http://download.jboss.org/jbosstools/static/neon/development/updates/core... > * http://download.jboss.org/jbosstools/static/neon/development/updates/core... > * http://download.jboss.org/jbosstools/static/neon/development/updates/core... > * http://download.jboss.org/jbosstools/static/neon/development/updates/core... > So, when qual != staging, need to also check for these files when running https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/p... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23388) add checks for jbosstools src zip+sha and browsersim-standalone.zip+sha

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23388?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-23388. ------------------------------ Resolution: Done Add fixversion and re-close. > add checks for jbosstools src zip+sha and browsersim-standalone.zip+sha > ----------------------------------------------------------------------- > > Key: JBIDE-23388 > URL: https://issues.jboss.org/browse/JBIDE-23388 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.2.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM2 > > > When releasing AM2, 4 files were not checked and therefore were not published. > * http://download.jboss.org/jbosstools/static/neon/development/updates/core... > * http://download.jboss.org/jbosstools/static/neon/development/updates/core... > * http://download.jboss.org/jbosstools/static/neon/development/updates/core... > * http://download.jboss.org/jbosstools/static/neon/development/updates/core... > So, when qual != staging, need to also check for these files when running https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/p... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23398) check Import-Package declarations to find more ui deps in core plugins

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-23398: ---------------------------------- Summary: check Import-Package declarations to find more ui deps in core plugins Key: JBIDE-23398 URL: https://issues.jboss.org/browse/JBIDE-23398 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: build, common Affects Versions: 4.4.2.AM2 Reporter: Nick Boldt Current enforcer is good in that it finds Require-Bundle paths of dependencies. But we should really be checking Import-Package relationships too, since some plugins (eg., openshift.client) don't use Require-Bundle at all. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23398) check Import-Package declarations to find more ui deps in core plugins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23398?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-23398: ---------------------------------- Assignee: Rob Stryker > check Import-Package declarations to find more ui deps in core plugins > ---------------------------------------------------------------------- > > Key: JBIDE-23398 > URL: https://issues.jboss.org/browse/JBIDE-23398 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, common > Affects Versions: 4.4.2.AM2 > Reporter: Nick Boldt > Assignee: Rob Stryker > Fix For: 4.4.2.AM3 > > > Current enforcer is good in that it finds Require-Bundle paths of dependencies. > But we should really be checking Import-Package relationships too, since some plugins (eg., openshift.client) don't use Require-Bundle at all. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23397) For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [server]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23397?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-23397: ---------------------------------- Assignee: Rob Stryker > For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [server] > --------------------------------------------------------------- > > Key: JBIDE-23397 > URL: https://issues.jboss.org/browse/JBIDE-23397 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.4.2.AM3 > > > For JBIDE 4.4.2.AM3 [server]: The following core plugins depend on UI plugins directly or indirectly. {code}[CoreUIDependency] org.jboss.ide.eclipse.as.classpath.core is a Core plugin, but depends on these UI plugins directly or transitively: > > org.eclipse.ui > > org.eclipse.ui.navigator > > org.eclipse.wst.server.ui > > org.eclipse.ui.ide > > org.eclipse.wst.common.modulecore.ui > > org.jboss.ide.eclipse.archives.ui > > org.jboss.ide.eclipse.as.ui > -- > [CoreUIDependency] org.jboss.ide.eclipse.as.rse.core is a Core plugin, but depends on these UI plugins directly or transitively: > > org.eclipse.ui > > org.eclipse.ui.navigator > > org.eclipse.wst.server.ui > > org.eclipse.ui.ide > > org.eclipse.wst.common.modulecore.ui > > org.jboss.ide.eclipse.archives.ui > > org.jboss.ide.eclipse.as.ui > -- > [CoreUIDependency] org.jboss.tools.as.test.core is a Core plugin, but depends on these UI plugins directly or transitively: > > org.eclipse.rse.ui > > org.eclipse.jdt.ui > > org.jboss.ide.eclipse.as.rse.ui > > org.eclipse.wst.server.ui > > org.eclipse.wst.xml.ui.infopop > > org.eclipse.wst.web.ui > > org.jboss.tools.jmx.jvmmonitor.ui > > org.eclipse.wst.common.project.facet.ui > > org.eclipse.wst.common.modulecore.ui > > org.eclipse.jdt.debug.ui > > org.eclipse.ui.browser > > org.eclipse.ui.views > > org.jboss.ide.eclipse.as.ui.mbeans > > org.eclipse.jst.j2ee.ui > > org.eclipse.wst.xml.ui > > org.jboss.ide.eclipse.as.wtp.ui > > org.eclipse.ui.editors > > org.jboss.tools.foundation.ui > > org.eclipse.rse.files.ui > > org.eclipse.jst.server.ui > > org.eclipse.jst.common.project.facet.ui > > org.jboss.ide.eclipse.archives.ui > > org.eclipse.ui.ide > > org.jboss.ide.eclipse.as.ui > > org.jboss.tools.runtime.ui > > org.eclipse.ui.views.log > > org.jboss.ide.eclipse.as.classpath.ui > > org.eclipse.ui.workbench.texteditor > > org.eclipse.ui > > org.eclipse.ui.navigator > > org.eclipse.ui.console > > org.eclipse.wst.sse.ui > > org.eclipse.debug.ui > > org.eclipse.wst.common.frameworks.ui > > org.jboss.tools.jmx.ui > > org.eclipse.ui.views.properties.tabbed > > org.eclipse.ui.forms{code} > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for server task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23395) For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [hibernate]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23395?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-23395: ---------------------------------- Assignee: Koen Aers > For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [hibernate] > ------------------------------------------------------------------ > > Key: JBIDE-23395 > URL: https://issues.jboss.org/browse/JBIDE-23395 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Nick Boldt > Assignee: Koen Aers > Priority: Blocker > Labels: task > Fix For: 4.4.2.AM3 > > > For JBIDE 4.4.2.AM3 [hibernate]: The following core plugins depend on UI plugins directly or indirectly. {code}[CoreUIDependency] org.jboss.tools.hibernate.jpt.core is a Core plugin, but depends on these UI plugins directly or transitively: > > org.eclipse.ant.ui > > org.eclipse.jdt.ui > > org.eclipse.ui.editors > > org.eclipse.ui.ide > > org.eclipse.datatools.connectivity.ui > > org.eclipse.ui.workbench.texteditor > > org.eclipse.ui > > org.eclipse.ui.navigator > > org.eclipse.ui.console > > org.eclipse.ui.workbench > > org.eclipse.debug.ui > > org.eclipse.wst.common.project.facet.ui > > org.eclipse.jdt.debug.ui > > org.eclipse.ui.views > > org.eclipse.ui.forms{code} > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for hibernate task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 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 October 2016