February 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-3641) Installer - initial run fails, log generated, subsequent run is successful

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3641?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3641: ------------------------------- Attachment: install.log > Installer - initial run fails, log generated, subsequent run is successful > -------------------------------------------------------------------------- > > Key: JBDS-3641 > URL: https://issues.jboss.org/browse/JBDS-3641 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.GA > Environment: Windows 10 > Reporter: Len DiMaggio > Assignee: Denis Golovin > Attachments: install.log > > > This problem is seen intermittently. Sometimes the initial run of the installer fails - but the subsequent run succeeds. See attached install.log. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3641) Installer - initial run fails, log generated, subsequent run is successful

by Len DiMaggio (JIRA)

Len DiMaggio created JBDS-3641: ---------------------------------- Summary: Installer - initial run fails, log generated, subsequent run is successful Key: JBDS-3641 URL: https://issues.jboss.org/browse/JBDS-3641 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: installer Affects Versions: 9.1.0.GA Environment: Windows 10 Reporter: Len DiMaggio Assignee: Denis Golovin This problem is seen intermittently. Sometimes the initial run of the installer fails - but the subsequent run succeeds. See attached install.log. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21737) Error while selecting a project in the OpenShift Explorer view

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21737?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21737: ------------------------------------- No I never experienced that problem. > Error while selecting a project in the OpenShift Explorer view > -------------------------------------------------------------- > > Key: JBIDE-21737 > URL: https://issues.jboss.org/browse/JBIDE-21737 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > > I have the following exception *many times* in the console when I select a project in the OpenShift Explorer view: > {code} > org.eclipse.core.commands.common.NotDefinedException: Cannot get the parent identifier from an undefined context. org.jboss.tools.openshift.explorer.context.connection > at org.eclipse.core.commands.contexts.Context.getParentId(Context.java:197) > at org.eclipse.e4.ui.bindings.internal.ContextSet$CComp.getLevel(ContextSet.java:49) > at org.eclipse.e4.ui.bindings.internal.ContextSet$CComp.compare(ContextSet.java:38) > at org.eclipse.e4.ui.bindings.internal.ContextSet$CComp.compare(ContextSet.java:1) > at java.util.TimSort.binarySort(TimSort.java:292) > at java.util.TimSort.sort(TimSort.java:217) > at java.util.Arrays.sort(Arrays.java:1512) > at java.util.ArrayList.sort(ArrayList.java:1454) > at java.util.Collections.sort(Collections.java:175) > at org.eclipse.e4.ui.bindings.internal.ContextSet.<init>(ContextSet.java:77) > at org.eclipse.e4.ui.bindings.internal.BindingTableManager.createContextSet(BindingTableManager.java:90) > at org.eclipse.e4.ui.bindings.internal.BindingServiceImpl.setContextIds(BindingServiceImpl.java:177) > at sun.reflect.GeneratedMethodAccessor27.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) > at org.eclipse.e4.core.internal.contexts.ContextObjectSupplier$ContextInjectionListener.update(ContextObjectSupplier.java:90) > at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(TrackableComputationExt.java:111) > at org.eclipse.e4.core.internal.contexts.EclipseContext.processScheduled(EclipseContext.java:341) > at org.eclipse.e4.core.internal.contexts.EclipseContext.set(EclipseContext.java:356) > at org.eclipse.e4.ui.internal.services.ContextContextService.activateContext(ContextContextService.java:56) > at org.eclipse.ui.internal.contexts.ContextService.activateContext(ContextService.java:170) > at org.eclipse.ui.internal.contexts.ContextService.activateContext(ContextService.java:102) > at org.jboss.tools.openshift.internal.common.ui.explorer.OpenShiftExplorerView$Contexts.activate(OpenShiftExplorerView.java:201) > at org.jboss.tools.openshift.internal.common.ui.explorer.OpenShiftExplorerView$OpenShiftExplorerContextsHandler$2.selectionChanged(OpenShiftExplorerView.java:187) > at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:163) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173) > at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:160) > at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2197) > at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1228) > at org.eclipse.ui.navigator.CommonViewer.handleSelect(CommonViewer.java:461) > at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1257) > at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:242) > at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:236) > at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:408) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4230) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1499) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072) > at org.eclipse.swt.widgets.Display.applicationNextEventMatchingMask(Display.java:5045) > at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5432) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) > at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:227) > at org.eclipse.swt.widgets.Widget.mouseDownSuper(Widget.java:1121) > at org.eclipse.swt.widgets.Tree.mouseDownSuper(Tree.java:2066) > at org.eclipse.swt.widgets.Widget.mouseDown(Widget.java:1113) > at org.eclipse.swt.widgets.Control.mouseDown(Control.java:2571) > at org.eclipse.swt.widgets.Tree.mouseDown(Tree.java:2034) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5692) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) > at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:227) > at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2130) > at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2337) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5756) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) > at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5193) > at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5342) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) > at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3695) > 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) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3617) Cannot run vagrant after running installer

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3617?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3617: ------------------------------- Component/s: installer (was: installerr) > Cannot run vagrant after running installer > ------------------------------------------ > > Key: JBDS-3617 > URL: https://issues.jboss.org/browse/JBDS-3617 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Environment: Windows 10 > Reporter: Len DiMaggio > Assignee: Rob Stryker > Priority: Blocker > Labels: havoc > Attachments: Vagrant.png > > > See attached screenshot - the same error is seen when running with the CDK configured as a runtime - or by running vagrant/vagrant.bat form the CLI after running the installer. > Exception occurred executing command line. > {{Cannot run program c:\DeveloperPlatform\vagrant\bin\vagrant) (in directory {{C:\DeveloperPlatform\cdk\plugins): CreateProcess error=193, %1 is not a valid Win32 application}} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3616) Installer is rejecting a valid user account - CDK error is indicated in debugger, but no error is logged

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3616?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-3616: ------------------------------ Component/s: installer > Installer is rejecting a valid user account - CDK error is indicated in debugger, but no error is logged > --------------------------------------------------------------------------------------------------------- > > Key: JBDS-3616 > URL: https://issues.jboss.org/browse/JBDS-3616 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Reporter: Len DiMaggio > Labels: havoc > Fix For: 9.1.0.CR1 > > Attachments: Screenshot (25).png > > > I have been seeing this problem for several days, both for when the installer is built from source and when the installer is downloaded from: http://machydra.tpb.lab.eng.brq.redhat.com:8080/view/Developer%20Tooling/... > See the attached screenshot - the user account - that had previously been used successfully - is now being rejected with an error of "invalid account information" - no additional information or error is logged - the install log only contains: > ----------------------------------------------------------------- > Tue, 26 Jan 2016 18:08:01 GMT-Developer Platform installer v0.0.2 > ----------------------------------------------------------------- -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3617) Cannot run vagrant after running installer

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3617?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3617: ------------------------------- Component/s: installerr > Cannot run vagrant after running installer > ------------------------------------------ > > Key: JBDS-3617 > URL: https://issues.jboss.org/browse/JBDS-3617 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installerr > Environment: Windows 10 > Reporter: Len DiMaggio > Assignee: Rob Stryker > Priority: Blocker > Labels: havoc > Attachments: Vagrant.png > > > See attached screenshot - the same error is seen when running with the CDK configured as a runtime - or by running vagrant/vagrant.bat form the CLI after running the installer. > Exception occurred executing command line. > {{Cannot run program c:\DeveloperPlatform\vagrant\bin\vagrant) (in directory {{C:\DeveloperPlatform\cdk\plugins): CreateProcess error=193, %1 is not a valid Win32 application}} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3619) Script authorization error

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3619?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3619: ------------------------------- Component/s: installer > Script authorization error > -------------------------- > > Key: JBDS-3619 > URL: https://issues.jboss.org/browse/JBDS-3619 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Reporter: Shane Bryzak > Labels: havoc > Attachments: screenshot.png > > > !screenshot.png|thumbnail! > The above error happens after all components have been downloaded. Running Windows 10. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3618) Progress does not reflect actual amount of work done

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3618?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3618: ------------------------------- Component/s: installer > Progress does not reflect actual amount of work done > ---------------------------------------------------- > > Key: JBDS-3618 > URL: https://issues.jboss.org/browse/JBDS-3618 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Reporter: Jan Richter > Priority: Minor > Labels: havoc > > It seems the current way the progress tracking is implemented is simply by giving an initial time estimate for each component. The progress bars then just count down the supplied time with no relation to the actual progress achieved. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3620) Account page should take into consideration that login request can be long term operation

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3620?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3620: ------------------------------- Component/s: installer > Account page should take into consideration that login request can be long term operation > ----------------------------------------------------------------------------------------- > > Key: JBDS-3620 > URL: https://issues.jboss.org/browse/JBDS-3620 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Critical > Labels: havoc > Fix For: 9.1.0.CR1 > > > Would be good to: > 1. Show progress animation; > 2. Lock [Log In] button; > 3. Have a timeout for login operation with error show in the end and button unlocked for another attempt. > Currently auth fails in browser with error below > {code}Gateway Timeout > The proxy server did not receive a timely response from the upstream server. > Reference #1.5434d417.1452674127.644f0c55 > {code} > which makes installer to look like being in broken state: > - no errors; > - [Log In] can be pressed many times without any reaction -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3621) Installer - if a "Developer-Platform" directory exists - presents a blank white dialog window - no error is logged

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3621?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3621: ------------------------------- Component/s: installer > Installer - if a "Developer-Platform" directory exists - presents a blank white dialog window - no error is logged > ------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-3621 > URL: https://issues.jboss.org/browse/JBDS-3621 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Reporter: Len DiMaggio > Labels: havoc > Fix For: 9.1.0.CR1 > > Attachments: Screenshot (24).png > > > See attached screenshot - if there is an existing Developer-Platform directory - the installer presents the blank white dialog. No error message is logged or displayed for the user. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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