April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22189) Unhandled event loop exception when selecting builder image in properties view.

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22189?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-22189: ----------------------------------- Assignee: Viacheslav Kabanovich > Unhandled event loop exception when selecting builder image in properties view. > ------------------------------------------------------------------------------- > > Key: JBIDE-22189 > URL: https://issues.jboss.org/browse/JBIDE-22189 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Environment: JBDS 9.1.0.CR1c > Reporter: Radim Hopp > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha1 > > > Showing "Builds" in properties view and then selecting "Builder Image", Unhandled event loop exception is thrown: > {noformat:title=Unhandled event loop exception} > org.eclipse.core.runtime.AssertionFailedException: assertion failed: > at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110) > at org.eclipse.core.runtime.Assert.isTrue(Assert.java:96) > at org.eclipse.jface.viewers.TextCellEditor.doSetValue(TextCellEditor.java:231) > at org.eclipse.jface.viewers.CellEditor.setValue(CellEditor.java:861) > at org.eclipse.ui.views.properties.PropertySheetEntry.getEditor(PropertySheetEntry.java:375) > at org.eclipse.ui.views.properties.PropertySheetViewer.activateCellEditor(PropertySheetViewer.java:166) > at org.eclipse.ui.views.properties.PropertySheetViewer.handleSelect(PropertySheetViewer.java:738) > at org.eclipse.ui.views.properties.PropertySheetViewer.access$8(PropertySheetViewer.java:718) > at org.eclipse.ui.views.properties.PropertySheetViewer$5.widgetDefaultSelected(PropertySheetViewer.java:813) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:119) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139) > 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:380) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) > 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:497) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608) > at org.eclipse.equinox.launcher.Main.run(Main.java:1515) > at org.eclipse.equinox.launcher.Main.main(Main.java:1488) > {noformat} > I have tried it with eap64-basic-s2i and eap64-mysql-persistent-s2i templates. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-718) Getting Started / Readme for new CDK users

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-718?page=com.atlassian.jira.plug... ] Alexey Kazakov commented on TOOLSDOC-718: ----------------------------------------- Thanks Martin for the clarification, but this is exactly I mentioned before that we should describe these workflows separately: 1. Installing JBDS & CDK using the installer 1.a Getting started with CDK/OS after #1 completed. 2. Installing JBDS (covered by JBDS doc) and CDK (covered by CDK guide) manually 2.a Getting started with CDK/OS after #2 completed (this use case has important differences comparing to #1) 1b/2b Using OS in JBDS > Getting Started / Readme for new CDK users > ------------------------------------------- > > Key: TOOLSDOC-718 > URL: https://issues.jboss.org/browse/TOOLSDOC-718 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 9.1 CR1 > Reporter: Nick Boldt > Assignee: Misha Ali > Labels: Havoc > Fix For: 9.1 GA > > > See JBDS-3738. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3838) Cannot install CDK. Installer prompts to setup VAGRANT_HOME if there is space in path and then it ignores it and fails

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3838?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3838: ------------------------------------- I can replicate that, setting VAGRANT_HOME does fix validation in installer, but CDK install fails, because it use custom environment and does not pick up user environment variables. > Cannot install CDK. Installer prompts to setup VAGRANT_HOME if there is space in path and then it ignores it and fails > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3838 > URL: https://issues.jboss.org/browse/JBDS-3838 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Pavol Srna > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 10.0.0.Alpha1 > > Attachments: install.log, vagrant.log, vbox.log > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22192) Not working link when adding a server of type OpenShift 3

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22192?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22192: ------------------------------------ It is based on org.jboss.tools.foundation.ui.util.BrowserUtility which itself it based on Eclipse browser support. > Not working link when adding a server of type OpenShift 3 > --------------------------------------------------------- > > Key: JBIDE-22192 > URL: https://issues.jboss.org/browse/JBIDE-22192 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Environment: Windows > Reporter: Aurélien Pupier > Assignee: Jeff MAURY > Priority: Minor > Fix For: 4.4.0.Alpha1 > > Attachments: screenshot-1.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3838) Cannot install CDK. Installer prompts to setup VAGRANT_HOME if there is space in path and then it ignores it and fails

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3838?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3838: ------------------------------------- VAGRANT_HOME should be in *user* environment or it not going to be present in installer environment after installer restart. > Cannot install CDK. Installer prompts to setup VAGRANT_HOME if there is space in path and then it ignores it and fails > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3838 > URL: https://issues.jboss.org/browse/JBDS-3838 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Pavol Srna > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 10.0.0.Alpha1 > > Attachments: install.log, vagrant.log, vbox.log > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3792) Installer - All installed components should be added to the path

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3792?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3792: ------------------------------------- Len, jdk8 is configured through devstudio.ini, so it always used by devstudio, there is no need to add it to PATH. devstudio has it is own group in windows menu and also should not be on path. > Installer - All installed components should be added to the path > ---------------------------------------------------------------- > > Key: JBDS-3792 > URL: https://issues.jboss.org/browse/JBDS-3792 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: havoc > > The installer (jboss-devstudio-9.1.0.GA-v20160410-1849-B495-installer-eap) adds these components to the user's PATH: > C:\DeveloperPlatform\vagrant\bin; > c:\DeveloperPlatform\cdk\bin; > c:\DeveloperPlatform\vagrant\bin; > c:\DeveloperPlatform\cygwin\bin; > It does not add these to the PATH: > c:\DeveloperPlatform\jdk8\bin; > c:\DeveloperPlatform\developer-studio > If we don't add the JDK and JBDS to the PATH by default, then we should give the user the option to add these during the installation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3792) Installer - All installed components should be added to the path

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3792?page=com.atlassian.jira.plugin.... ] Denis Golovin resolved JBDS-3792. --------------------------------- Resolution: Rejected > Installer - All installed components should be added to the path > ---------------------------------------------------------------- > > Key: JBDS-3792 > URL: https://issues.jboss.org/browse/JBDS-3792 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: havoc > > The installer (jboss-devstudio-9.1.0.GA-v20160410-1849-B495-installer-eap) adds these components to the user's PATH: > C:\DeveloperPlatform\vagrant\bin; > c:\DeveloperPlatform\cdk\bin; > c:\DeveloperPlatform\vagrant\bin; > c:\DeveloperPlatform\cygwin\bin; > It does not add these to the PATH: > c:\DeveloperPlatform\jdk8\bin; > c:\DeveloperPlatform\developer-studio > If we don't add the JDK and JBDS to the PATH by default, then we should give the user the option to add these during the installation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3686) Installer is unpredictable - failing in diff actions

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3686?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3686: -------------------------------- Fix Version/s: 10.0.0.Alpha1 > Installer is unpredictable - failing in diff actions > ---------------------------------------------------- > > Key: JBDS-3686 > URL: https://issues.jboss.org/browse/JBDS-3686 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Environment: Windows 10, installer built from src > Reporter: Len DiMaggio > Assignee: Denis Golovin > Priority: Critical > Labels: havoc > Fix For: 10.0.0.Alpha1 > > Attachments: Attempt_1.png, Attempt_2.png, Attempt_3.png, install_log_1.txt, install_log_2.txt, install_log_3.txt > > > See attached log files and screenshots - installer faled in different locations on 3 attempts. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3806) Installer - reduce footer height to reveal more content

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3806?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3806: -------------------------------- Fix Version/s: 10.0.0.Alpha1 > Installer - reduce footer height to reveal more content > ------------------------------------------------------- > > Key: JBDS-3806 > URL: https://issues.jboss.org/browse/JBDS-3806 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.Beta2 > Reporter: Joshua Wilson > Assignee: Joshua Wilson > Priority: Blocker > Labels: havoc, ui > Fix For: 10.0.0.Alpha1 > > Attachments: confirm.png > > > The footer on the confirm page would look better if it cut into the display of one of the components to be installed. Also, remove the transparency. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3769) Remove JSPM from dependencies

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3769?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3769: -------------------------------- Fix Version/s: 10.0.0.Alpha1 > Remove JSPM from dependencies > ----------------------------- > > Key: JBDS-3769 > URL: https://issues.jboss.org/browse/JBDS-3769 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Priority: Critical > Labels: havoc > Fix For: 10.0.0.Alpha1 > > > After a change introduced in jspm 0.16.32 which caused our builds to fail (JBDS-3747) now another issue has arisen causing errors on npm install (both local and in CI environment). Even if this new issue is fixed in jspm, we would still have to face the first issue after updating. > Therefore I propose to remove jspm entirely. We only use a small fraction of its functionality and it needlessly complicates the build + causes major issues. Since such change is likely to be quite complex, we should slip it after the April release and use an existing quick fix in the mean time. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2016