August 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24803) Add JBoss DV 6.3 to Download Runtimes Wizard

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24803?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-24803: ---------------------------------- Git Pull Request: (was: https://github.com/jboss-developer/jboss-stacks/pull/59) > Add JBoss DV 6.3 to Download Runtimes Wizard > -------------------------------------------- > > Key: JBIDE-24803 > URL: https://issues.jboss.org/browse/JBIDE-24803 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Reporter: Radim Hopp > Assignee: Rob Stryker > > JBoss DV 6.2 was released 5 days ago. I guess it should be downloadable from Download Runtimes Wizard. > I've also created JDF-852. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24790) Connection wizard: "Override 'oc' location" text box does not expand when dialog is horizontally expanded

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24790?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-24790. ------------------------------ Verified in Devstudio 11.0.0.GA. Closing > Connection wizard: "Override 'oc' location" text box does not expand when dialog is horizontally expanded > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24790 > URL: https://issues.jboss.org/browse/JBIDE-24790 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard, openshift_v3 > Fix For: 4.5.0.Final > > Attachments: screenshot-1.png > > > When the connection editor is horizontally expanded, the override oc text box keep the same size and is not expanded (as opposed to the registry url and template namespace text boxes). > Furthermore the text field and browse button are not properly aligned with the right border, there's a gap. > !screenshot-1.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24775) Token field isn't automatically filled in after token extraction

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24775?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-24775. ------------------------------ Verified in Devstudio 11.0.0.GA. Closing > Token field isn't automatically filled in after token extraction > ---------------------------------------------------------------- > > Key: JBIDE-24775 > URL: https://issues.jboss.org/browse/JBIDE-24775 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Dmitrii Bocharov > Assignee: Andre Dietisheim > Fix For: 4.5.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24768) openshift connection wizard advanced section persists changes when canceled

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24768?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-24768. ------------------------------ Verified in Devstudio 11.0.0.GA. Closing > openshift connection wizard advanced section persists changes when canceled > --------------------------------------------------------------------------- > > Key: JBIDE-24768 > URL: https://issues.jboss.org/browse/JBIDE-24768 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.5.0.Final > > > When you have an openshift connection, if you right-click on it and edit it, you can then change it's properties. If you expand the advanced section, and make changes, and then cancel the wizard, all changes are persisted when they should not be. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24802) Lots of unnecessary errors in Error Log when filling oc location in ConnectionWizard

by Radim Hopp (JIRA)

Radim Hopp created JBIDE-24802: ---------------------------------- Summary: Lots of unnecessary errors in Error Log when filling oc location in ConnectionWizard Key: JBIDE-24802 URL: https://issues.jboss.org/browse/JBIDE-24802 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.5.0.Final Reporter: Radim Hopp Priority: Minor Attachments: Spectacle.F10835.png On-the-fly validation of "oc location" field in ConnectionWizardPage puts lot of errors into error log. I think that the on the fly validation should not be so agressive. !Spectacle.F10835.png! And another thing: Is there any reason why Finish is enabled even when there is not valid value in oc location field? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4462) DevSuite Installer should cache downloaded files in platform specific application data folder

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4462?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-4462. ----------------------------- Verified in build #300 > DevSuite Installer should cache downloaded files in platform specific application data folder > --------------------------------------------------------------------------------------------- > > Key: JBDS-4462 > URL: https://issues.jboss.org/browse/JBDS-4462 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 11.0.0.AM2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: New_and_noteworthy > Fix For: 11.0.0.GA > > > Current implementation downloads files in user specific temp folder ~/AppData/Local/Temp and sometimes windows removes those files during installation which causes random installation failures for various components. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24539) Explorer, Properties: User should be able to see what OpenShift version a connection is

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24539?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-24539. ------------------------------ Verified in Devstudio 11.0.0.GA. Closingl > Explorer, Properties: User should be able to see what OpenShift version a connection is > --------------------------------------------------------------------------------------- > > Key: JBIDE-24539 > URL: https://issues.jboss.org/browse/JBIDE-24539 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.AM1 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: explorer, openshift_v2, openshift_v3, properties > Fix For: 4.5.0.Final > > Attachments: image-2017-06-06-11-54-02-000.png > > > steps: > # ASSERT: have a connection to an OpenShift 3 and an OpenShift 2 server respectively > # EXEC: look at the entries in the explorer and in the Properties view > Result: > !image-2017-06-06-11-54-02-000.png! > You have no idea about the versions of the OpenShift servers of the connections that you have. You may only figure out implicitly by the "Domains" displayed in the properties for the OpenShift 2 connection. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24745) Client: use final client jar for the Devtools Final build

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24745?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-24745. ------------------------------ 3.4.0.Final client is used in Devstudio 11.0.0.GA. Closing. > Client: use final client jar for the Devtools Final build > --------------------------------------------------------- > > Key: JBIDE-24745 > URL: https://issues.jboss.org/browse/JBIDE-24745 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Labels: client, openshift_v3 > Fix For: 4.5.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24774) ClassCastException while creating new Openshift connection

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24774?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-24774. ------------------------------ Verified in Devstudio 11.0.0.GA. Closing. > ClassCastException while creating new Openshift connection > ---------------------------------------------------------- > > Key: JBIDE-24774 > URL: https://issues.jboss.org/browse/JBIDE-24774 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Dmitrii Bocharov > Assignee: Andre Dietisheim > Priority: Blocker > Labels: connection_wizard, openshift_v3 > Fix For: 4.5.0.Final > > Attachments: screencast.webm > > > {code:java} > java.lang.RuntimeException: java.lang.ClassCastException: org.jboss.tools.openshift.common.core.connection.NewConnectionMarker cannot be cast to org.jboss.tools.openshift.core.connection.Connection > at org.eclipse.core.internal.databinding.beans.BeanPropertyHelper.readProperty(BeanPropertyHelper.java:102) > at org.eclipse.core.internal.databinding.beans.BeanValueProperty.doGetValue(BeanValueProperty.java:49) > at org.eclipse.core.databinding.property.value.ValueProperty.getValue(ValueProperty.java:62) > at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.notifyIfChanged(SimplePropertyObservableValue.java:121) > at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.doGetValue(SimplePropertyObservableValue.java:102) > at org.eclipse.core.databinding.observable.value.AbstractObservableValue.getValue(AbstractObservableValue.java:88) > at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.getValue(DecoratingObservableValue.java:109) > at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.getValue(DecoratingObservableValue.java:109) > at org.eclipse.core.databinding.ValueBinding$3.run(ValueBinding.java:169) > 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.databinding.ValueBinding.doUpdate(ValueBinding.java:162) > at org.eclipse.core.databinding.ValueBinding.updateModelToTarget(ValueBinding.java:127) > at org.eclipse.core.databinding.DataBindingContext.updateTargets(DataBindingContext.java:464) > at org.jboss.tools.common.ui.WizardUtils.runInWizard(WizardUtils.java:216) > at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPage.connect(ConnectionWizardPage.java:385) > at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizard.performFinish(ConnectionWizard.java:77) > at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:778) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:417) > at org.eclipse.jface.dialogs.Dialog.lambda$0(Dialog.java:619) > at org.eclipse.swt.events.SelectionListener$1.widgetSelected(SelectionListener.java:81) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5252) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1348) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4522) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4107) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:818) > at org.eclipse.jface.window.Window.open(Window.java:794) > at org.jboss.tools.openshift.internal.common.ui.explorer.OpenShiftExplorerView$2.widgetSelected(OpenShiftExplorerView.java:140) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5252) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1348) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1374) > at org.eclipse.swt.widgets.Widget.sendSelectionEvent(Widget.java:1488) > at org.eclipse.swt.widgets.Link.gtk_button_release_event(Link.java:384) > at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1956) > at org.eclipse.swt.widgets.Control.windowProc(Control.java:6168) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5512) > 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:9251) > at org.eclipse.swt.widgets.Display.eventProc(Display.java:1252) > 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:2110) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4105) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1155) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1044) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153) > at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151) > 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.refle > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4498) Multiple BundleExceptions in the log

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4498?page=com.atlassian.jira.plugin.... ] Lukáš Valach closed JBDS-4498. ------------------------------ Verified in 11.0-0.20170804.2132.el7, problem is resolved, thank you. Closing. > Multiple BundleExceptions in the log > ------------------------------------ > > Key: JBDS-4498 > URL: https://issues.jboss.org/browse/JBDS-4498 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: rpm > Affects Versions: 11.0.0.GA > Reporter: Lukáš Valach > Assignee: Nick Boldt > Fix For: 11.0.0.GA > > Attachments: rh-eclipse47.log_clean_start_strict.txt > > > There are multiple errors in the log after start of 11.0-0.20170804.0022.el7. See the log: > [^rh-eclipse47.log_clean_start_strict.txt] > Interesting is that these errors dissapeared after installation of everything from Central. Maybe we really missing something? > Start of clean Devstudio (and then installation from Central): https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Start after installation from Central (no bundleException): > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 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 August 2017