November 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-4163) Exception 'undefined has no version property' is reported to electron console during detection phase

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4163?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4163: -------------------------------- Fix Version/s: 10.2.0.AM3 > Exception 'undefined has no version property' is reported to electron console during detection phase > ---------------------------------------------------------------------------------------------------- > > Key: JBDS-4163 > URL: https://issues.jboss.org/browse/JBDS-4163 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.2.0.AM3 > Environment: Windows > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.2.0.AM3 > > > This error appears if for component that have no detection feature or haven't been detected on confirmation page. They weren't reported before and probably related to nodejs update to latest version. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ERT-447) NullPointerException in DockerConnectionManager.findConnection [EBZ#507154]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-447: --------------------------------------- Summary: NullPointerException in DockerConnectionManager.findConnection [EBZ#507154] Key: ERT-447 URL: https://issues.jboss.org/browse/ERT-447 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot Fix For: Neon.2 (4.6) The following problem was reported via the automated error reporting: Message: Unhandled exception: null java.lang.NullPointerException: null at org.eclipse.linuxtools.docker.core.DockerConnectionManager.findConnection(DockerConnectionManager.java:174) at org.eclipse.linuxtools.internal.docker.ui.wizards.NewDockerConnectionPage$ConnectionNameValidator.validate(NewDockerConnectionPage.java:878) at org.eclipse.linuxtools.internal.docker.ui.wizards.NewDockerConnectionPage$UnixSocketValidator.validate(NewDockerConnectionPage.java:910) at org.eclipse.core.databinding.validation.MultiValidator$1ValidationRunnable.run(MultiValidator.java:255) at org.eclipse.core.databinding.observable.ObservableTracker.runAndMonitor(ObservableTracker.java:109) at org.eclipse.core.databinding.validation.MultiValidator.revalidate(MultiValidator.java:267) at org.eclipse.core.databinding.validation.MultiValidator$DependencyListener.handleChange(MultiValidator.java:157) at org.eclipse.core.databinding.observable.ChangeEvent.dispatch(ChangeEvent.java:42) at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:117) at org.eclipse.core.databinding.observable.AbstractObservable.fireChange(AbstractObservable.java:71) at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.fireValueChange(DecoratingObservableValue.java:60) at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.handleValueChange(DecoratingObservableValue.java:103) at org.eclipse.core.databinding.observable.value.DecoratingObservableValue$1.handleValueChange(DecoratingObservableValue.java:76) at org.eclipse.core.databinding.observable.value.ValueChangeEvent.dispatch(ValueChangeEvent.java:70) at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:117) at org.eclipse.core.databinding.observable.value.AbstractObservableValue.fireValueChange(AbstractObservableValue.java:82) at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.notifyIfChanged(SimplePropertyObservableValue.java:126) at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.access$3(SimplePropertyObservableValue.java:118) at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue$1$1.run(SimplePropertyObservableValue.java:70) at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:149) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:153) at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:171) at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue$1.handleEvent(SimplePropertyObservableValue.java:66) at org.eclipse.core.databinding.property.NativePropertyListener.fireChange(NativePropertyListener.java:69) at org.eclipse.core.internal.databinding.beans.BeanPropertyListener.propertyChange(BeanPropertyListener.java:50) at java.beans.PropertyChangeSupport.fire(PropertyChangeSupport.java:335) at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:328) at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:263) at org.eclipse.linuxtools.internal.docker.ui.databinding.BaseDatabindingModel.firePropertyChange(BaseDatabindingModel.java:42) at org.eclipse.linuxtools.internal.docker.ui.wizards.NewDockerConnectionPageModel.setConnectionName(NewDockerConnectionPageModel.java:81) at org.eclipse.linuxtools.internal.docker.ui.wizards.NewDockerConnectionPage$4.widgetSelected(NewDockerConnectionPage.java:738) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) Bundles: | org.eclipse.core.databinding | 1.6.0.v20160412-0910 | 1.6.0.v20160412-0910 | | org.eclipse.core.databinding.beans | 1.3.100.v20160509-1025 | 1.3.100.v20160509-1025 | | org.eclipse.core.databinding.observable | 1.6.0.v20160511-1747 | 1.6.0.v20160511-1747 | | org.eclipse.core.databinding.property | 1.6.0.v20160427-0852 | 1.6.0.v20160427-0852 | | org.eclipse.core.runtime | 3.12.0.v20160606-1342 | 3.12.0.v20160606-1342 | | org.eclipse.linuxtools.docker.core | 2.1.0.201609141916 | 2.1.0.201609141916 | | org.eclipse.linuxtools.docker.ui | 2.1.0.201609141916 | 2.1.0.201609141916 | | org.eclipse.swt | 3.105.1.v20160907-0248 | 3.105.1.v20160907-0248 | Operating Systems: | Windows | 6.1.0 | 6.1.0 | The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/5807a... for the latest data. Thank you for your assistance. Your friendly error-reports-inbox. Created on behalf of xcoulon(a)xxxxxx.xxx -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ERT-448) AssertionFailedException below ImageBuildDialog.createDialogArea (thrown in StructuredViewer.assertElementsNotNull) [EBZ#507164]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-448: --------------------------------------- Summary: AssertionFailedException below ImageBuildDialog.createDialogArea (thrown in StructuredViewer.assertElementsNotNull) [EBZ#507164] Key: ERT-448 URL: https://issues.jboss.org/browse/ERT-448 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot The following problem was reported via the automated error reporting: Message: Unhandled event loop exception org.eclipse.core.runtime.AssertionFailedException: null argument: at org.eclipse.jface.viewers.StructuredViewer.assertElementsNotNull(StructuredViewer.java:586) at org.eclipse.jface.viewers.StructuredViewer.getRawChildren(StructuredViewer.java:1002) at org.eclipse.jface.viewers.StructuredViewer.getFilteredChildren(StructuredViewer.java:907) at org.eclipse.jface.viewers.StructuredViewer.getSortedChildren(StructuredViewer.java:1084) at org.eclipse.jface.viewers.AbstractListViewer.inputChanged(AbstractListViewer.java:318) at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:286) at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1696) at org.eclipse.linuxtools.internal.docker.ui.wizards.ImageBuildDialog.createDialogArea(ImageBuildDialog.java:118) at org.eclipse.jface.dialogs.Dialog.createContents(Dialog.java:767) at org.eclipse.jface.window.Window.create(Window.java:426) at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1095) at org.eclipse.jface.window.Window.open(Window.java:783) at org.eclipse.linuxtools.internal.docker.ui.launch.BuildDockerImageShortcut.createConfiguration(BuildDockerImageShortcut.java:109) at org.eclipse.linuxtools.internal.docker.ui.launch.BaseResourceAwareLaunchShortcut.findLaunchConfiguration(BaseResourceAwareLaunchShortcut.java:84) at org.eclipse.linuxtools.internal.docker.ui.launch.BuildDockerImageShortcut.launch(BuildDockerImageShortcut.java:61) at org.eclipse.linuxtools.internal.docker.ui.launch.BaseResourceAwareLaunchShortcut.launch(BaseResourceAwareLaunchShortcut.java:41) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchShortcutExtension.launch(LaunchShortcutExtension.java:431) at org.eclipse.debug.internal.ui.actions.LaunchShortcutAction.run(LaunchShortcutAction.java:74) at org.eclipse.debug.internal.ui.actions.LaunchShortcutAction.runWithEvent(LaunchShortcutAction.java:123) 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:84) Bundles: | org.eclipse.debug.ui | 3.11.200.v20160518-1858 | 3.11.200.v20160518-1858 | | org.eclipse.jface | 3.12.0.v20160518-1929 | 3.12.0.v20160518-1929 | | org.eclipse.linuxtools.docker.ui | 2.1.0.201609141916 | 2.1.0.201609141916 | | org.eclipse.swt | 3.105.0.v20160603-0902 | 3.105.0.v20160603-0902 | Operating Systems: | Windows | 10.0.0 | 10.0.0 | The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/580dd... for the latest data. Thank you for your assistance. Your friendly error-reports-inbox. Created on behalf of xcoulon(a)xxxxxx.xxx -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23467) Unnecessary GWT files

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23467?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-23467. --------------------------------- Resolution: Done Fixed in master > Unnecessary GWT files > --------------------- > > Key: JBIDE-23467 > URL: https://issues.jboss.org/browse/JBIDE-23467 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, rpm > Affects Versions: 4.4.2.AM3 > Environment: RHEL7 64bit > rh-eclipse46-devstudio-10.2-0.20161103.1913.el7.x86_64.rpm > Reporter: Lukáš Valach > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.4.2.Final > > > GWT feature and plugin has been removed in [JBIDE-23414|https://issues.jboss.org/browse/JBIDE-23414], but there are still GWT files. > {code} > [lvalach@localhost rh]$ sudo find . -iname '*gwt*' > ./rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.central_2.1.2.v20160922-1945/icons/gwt_background.png > ./rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.central_2.1.2.v20160922-1945/org/jboss/tools/central/wizards/NewGwtProjectWizard.class > {code} > These files are unnecessary I guess. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23470) Server Adapter: stuck restarting in debug mode

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23470?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-23470: ------------------------------------- I replicated very similar behavior on kitchensink on openshift behind cdk 05-oct-2016. I didn't see such a stack trace, but the behavior was identical. > Server Adapter: stuck restarting in debug mode > ---------------------------------------------- > > Key: JBIDE-23470 > URL: https://issues.jboss.org/browse/JBIDE-23470 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Priority: Critical > Attachments: failed-to-detect-pod.png, server-adapter-stuck-starting.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23469) Include ISettings functions in Configuration

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23469?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-23469: ------------------------------ Summary: Include ISettings functions in Configuration (was: Replace occurrences of ISettings#getDefaultCatalogName() with Environment#getDefaultCatalog()) > Include ISettings functions in Configuration > -------------------------------------------- > > Key: JBIDE-23469 > URL: https://issues.jboss.org/browse/JBIDE-23469 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.4.2.AM3 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.2.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23469) Include ISettings functions in Configuration

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23469?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-23469: ------------------------------ Story Points: 16 (was: 2) > Include ISettings functions in Configuration > -------------------------------------------- > > Key: JBIDE-23469 > URL: https://issues.jboss.org/browse/JBIDE-23469 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.4.2.AM3 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.2.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23470) Server Adapter: stuck restarting in debug mode

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23470?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-23470 at 11/7/16 9:36 AM: ------------------------------------------------------------------- [~bdshadow] just tested origin source 1.3.1, and he cannot replicate the problem: {quote} tested just with OS origin (no CDK) used 1.3.1: https://github.com/openshift/origin/releases/tag/v1.3.1 everything works fine {quote} both CDKs apparently use the same origin: * 7th of October: openshift v3.3.0.32 kubernetes v1.3.0+52492b4 * 4th of November openshift v3.3.0.32 kubernetes v1.3.0+52492b4 was (Author: adietish): [~bdshadow] just tested origin source 1.3.1, and he cannot replicate the problem: {quote} tested just with OS origin (no CDK) used 1.3.1: https://github.com/openshift/origin/releases/tag/v1.3.1 everything works fine {quote} > Server Adapter: stuck restarting in debug mode > ---------------------------------------------- > > Key: JBIDE-23470 > URL: https://issues.jboss.org/browse/JBIDE-23470 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Priority: Critical > Attachments: failed-to-detect-pod.png, server-adapter-stuck-starting.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23470) Server Adapter: stuck restarting in debug mode

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23470?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23470: ------------------------------------------ [~bdshadow] just tested origin source 1.3.1, and he cannot replicate the problem: {quote} tested just with OS origin (no CDK) used 1.3.1: https://github.com/openshift/origin/releases/tag/v1.3.1 everything works fine {quote} > Server Adapter: stuck restarting in debug mode > ---------------------------------------------- > > Key: JBIDE-23470 > URL: https://issues.jboss.org/browse/JBIDE-23470 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Priority: Critical > Attachments: failed-to-detect-pod.png, server-adapter-stuck-starting.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-953) SY - throw a known issue when detecting a wrong switchyard version in project creation test

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-953?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky resolved JBTIS-953. ------------------------------------- Resolution: Done > SY - throw a known issue when detecting a wrong switchyard version in project creation test > ------------------------------------------------------------------------------------------- > > Key: JBTIS-953 > URL: https://issues.jboss.org/browse/JBTIS-953 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE, switchyard > Affects Versions: 4.3.2.Final, 4.4.0.Alpha1 > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Fix For: 4.4.0.Final, 4.3.3.Final > > > Throw a known issue when detecting a wrong switchyard version in project creation test. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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 November 2016