May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22412) Enhance JobChainBuilder with conditions for starting the next job

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22412?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22412. --------------------------------- Verified in devstudio with build id: Alpha3-v20160531-0503-B5474. > Enhance JobChainBuilder with conditions for starting the next job > ----------------------------------------------------------------- > > Key: JBIDE-22412 > URL: https://issues.jboss.org/browse/JBIDE-22412 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha3 > > > For example, if the chain of jobs is loading content of a wizard or an editor, and user may close it before jobs are completed, there is no need to schedule the next job in the chain when the previous job is done. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22413) Connection Editor: dont launch further jobs if editor is already closed

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22413?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22413. --------------------------------- Verified in devstudio with build id: Alpha3-v20160531-0503-B5474. > Connection Editor: dont launch further jobs if editor is already closed > ----------------------------------------------------------------------- > > Key: JBIDE-22413 > URL: https://issues.jboss.org/browse/JBIDE-22413 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha3 > > > ASSERT: make sure that you have a server adapter > EXEC: open it in the server editor > ASSERT: the widgets in the openshift section are disabled, in the status bar (or progress view) you see a job "Loading projects..." running > EXEC: close the editor > ASSERT: nothing happens so far, but you see another job running "Setting connection, deploy..." -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22195) Docker-machine look-up does not work

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22195?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22195: --------------------------------------- The search button now works for me on mac with docker machine both with latest nightly of Docker Tools (http://download.eclipse.org/linuxtools/updates-docker-nightly/) and latest nightly of devstudio 10 (devstudio-10.0.0.Alpha3-v20160531-1024-B5476-installer-standalone.jar) > Docker-machine look-up does not work > ------------------------------------ > > Key: JBIDE-22195 > URL: https://issues.jboss.org/browse/JBIDE-22195 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, upstream > Affects Versions: 4.3.1.CR1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.4.0.Alpha2 > > > The {{Search...}} dialog for Docker Machines in the New Connection wizard in the Docker tooling does not work: a warning message appears in the Error Log view, saying : > {quote} > The 'docker-machine' command could not be located in /usr/bin:/bin:/usr/sbin:/sbin > {quote} > even though the preferences show that the {{docker-machine}} command is located in {{/usr/local/bin}}. > See https://bugs.eclipse.org/bugs/show_bug.cgi?id=493328 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22165) Deploy Docker wizard: Check "Add Route" checkbox for exposing services of docker image by default

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22165?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22165. --------------------------------- Verified in devstudio with build id: Alpha3-v20160531-0503-B5474. > Deploy Docker wizard: Check "Add Route" checkbox for exposing services of docker image by default > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-22165 > URL: https://issues.jboss.org/browse/JBIDE-22165 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Thomas Mäder > Labels: deploy_docker_wizard, docker, openshift_v3 > Fix For: 4.4.0.Alpha3 > > > I think usually users would like to expose their services of a docker image being deployed to OpenShift. In the Deploy Image to OpenShift wizard we have a wizard page where mapping of ports is happening and also exposing of services to routes by checking a checkbox "Add Route" is placed there. By default we have this checkbox unchecked, but maybe we should enable it by default. In my humble opinion in many use case there will be an existing docker image of some application and user would like to deploy it to OpenShift and check application whether it is working or use some features of OpenShift itself... > At the moment we don't have enabled exposing of OpenShift resources in tooling and therefore if user by accident or intentionally click on Finish button in Deploy Image to OpenShift wizard one page earlier (the one where env. vars, scaling and data volumes are located), it produce a running pod with service, but there is no route and it force user to swich to command line to use oc to expose a service to get a route. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22247) Reorganize context menus of OpenShift Resources in properties view

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22247?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22247. --------------------------------- Verified in devstudio with build id: Alpha3-v20160531-0503-B5474. > Reorganize context menus of OpenShift Resources in properties view > ------------------------------------------------------------------ > > Key: JBIDE-22247 > URL: https://issues.jboss.org/browse/JBIDE-22247 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: openshift_v3, properties, ux > Fix For: 4.4.0.Alpha3 > > Attachments: bc_cm.png, build_cm.png, dc_cm.png, pod_cm.png, rc_cm.png, route_cm.png, service_cm.png > > > Context menus of OpenShift resources in Properties view are quite messy. It could be ordered better. For reference check Eclipse guidelines on context menus of objects in views https://wiki.eclipse.org/User_Interface_Guidelines#Context_Menus_2 > See screenshots of context menus > *Build config* > !bc_cm.png! > *Build* > !build_cm.png! > *Deployment Config* > !dc_cm.png! > *Pod* > !pod_cm.png! > *Service* > !service_cm.png! > *Route* > !route_cm.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21477) Server adapter wizard: listed services wont change if I go back and select a different connection

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21477?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21477. --------------------------------- Verified in devstudio with build id: Alpha3-v20160531-0503-B5474. > Server adapter wizard: listed services wont change if I go back and select a different connection > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-21477 > URL: https://issues.jboss.org/browse/JBIDE-21477 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Andre Dietisheim > Assignee: Viacheslav Kabanovich > Labels: openshift_v3, server_adapter_wizard > Fix For: 4.4.0.Alpha3 > > Attachments: services.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3606) update branding for jbds 10.0 installer

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3606?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3606. ----------------------------- Looks good to me, closing. > update branding for jbds 10.0 installer > --------------------------------------- > > Key: JBDS-3606 > URL: https://issues.jboss.org/browse/JBDS-3606 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: installer > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 10.0.0.Alpha2 > > Attachments: installer-10.png > > > name and branding of JBDS set to change. Need the base izpack based installer to have an updated look. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22445) Server adapter wizard: NPE when finishing

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22445?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22445. --------------------------------- Verified in devstudio with build id: Alpha3-v20160531-0503-B5474. > Server adapter wizard: NPE when finishing > ------------------------------------------ > > Key: JBIDE-22445 > URL: https://issues.jboss.org/browse/JBIDE-22445 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Radim Hopp > Assignee: Viacheslav Kabanovich > Priority: Critical > Labels: openshift_v3, server_adapter_wizard > Fix For: 4.4.0.Alpha3 > > > I'm getting NPE when finishing New Server Wizard of Openshift 3 server adapter. > mlabuda was also able to reproduce this bug. > {noformat} > java.lang.NullPointerException > at org.eclipse.wst.server.ui.internal.wizard.TaskWizardPage.update(TaskWizardPage.java:126) > at org.jboss.tools.openshift.internal.ui.server.ServerSettingsWizardFragment$ServerSettingsWizardPageWrapper.setPageComplete(ServerSettingsWizardFragment.java:200) > at org.jboss.tools.openshift.internal.ui.server.ServerSettingsWizardPage.setComplete(ServerSettingsWizardPage.java:189) > at org.jboss.tools.openshift.internal.ui.server.ServerSettingsWizardPage$1.setComplete(ServerSettingsWizardPage.java:207) > at org.jboss.tools.openshift.internal.common.ui.databinding.FormPresenterSupport.handleComplete(FormPresenterSupport.java:243) > at org.jboss.tools.openshift.internal.common.ui.databinding.FormPresenterSupport.handleStatusChanged(FormPresenterSupport.java:232) > at org.jboss.tools.openshift.internal.common.ui.databinding.FormPresenterSupport.statusProviderChanged(FormPresenterSupport.java:200) > at org.jboss.tools.openshift.internal.common.ui.databinding.FormPresenterSupport.access$2(FormPresenterSupport.java:190) > at org.jboss.tools.openshift.internal.common.ui.databinding.FormPresenterSupport$4.handleValueChange(FormPresenterSupport.java:158) > 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.databinding.observable.value.ComputedValue.makeDirty(ComputedValue.java:240) > at org.eclipse.core.databinding.observable.value.ComputedValue$PrivateInterface.handleChange(ComputedValue.java:183) > 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.list.ObservableList.fireListChange(ObservableList.java:81) > at org.eclipse.core.databinding.observable.list.WritableList.remove(WritableList.java:235) > at org.eclipse.core.databinding.DataBindingContext.removeValidationStatusProvider(DataBindingContext.java:489) > at org.eclipse.core.databinding.DataBindingContext.removeBinding(DataBindingContext.java:476) > at org.eclipse.core.databinding.Binding.dispose(Binding.java:135) > at org.eclipse.core.databinding.ValueBinding.dispose(ValueBinding.java:269) > at org.eclipse.core.databinding.DataBindingContext.dispose(DataBindingContext.java:367) > at org.jboss.tools.openshift.internal.common.ui.utils.DataBindingUtils.dispose(DataBindingUtils.java:107) > at org.jboss.tools.openshift.internal.common.ui.wizard.AbstractOpenShiftWizardPage$1.widgetDisposed(AbstractOpenShiftWizardPage.java:79) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:124) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5208) > 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:1345) > at org.eclipse.swt.widgets.Widget.release(Widget.java:1153) > at org.eclipse.swt.widgets.Control.release(Control.java:3989) > at org.eclipse.swt.widgets.Widget.dispose(Widget.java:479) > at org.eclipse.swt.widgets.Shell.dispose(Shell.java:2660) > at org.eclipse.jface.window.Window.close(Window.java:330) > at org.eclipse.jface.dialogs.Dialog.close(Dialog.java:989) > at org.eclipse.jface.wizard.WizardDialog.hardClose(WizardDialog.java:853) > at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:798) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:423) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5208) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4542) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4132) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:818) > at org.eclipse.jface.window.Window.open(Window.java:794) > at org.eclipse.wst.server.ui.internal.actions.LaunchWizardAction.run(LaunchWizardAction.java:57) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:473) > 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) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5208) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4542) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4132) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:818) > at org.eclipse.jface.window.Window.open(Window.java:794) > at org.eclipse.wst.server.ui.internal.actions.LaunchWizardAction.run(LaunchWizardAction.java:57) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:473) > 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) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5208) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4542) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4132) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:818) > at org.eclipse.jface.window.Window.open(Window.java:794) > at org.eclipse.wst.server.ui.internal.actions.LaunchWizardAction.run(LaunchWizardAction.java:57) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:473) > 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) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5208) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4542) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4132) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1119) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1020) > 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:497) > 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) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22466) Bump all server plugins' BREE to JavaSE-1.8

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-22466: ----------------------------------- Summary: Bump all server plugins' BREE to JavaSE-1.8 Key: JBIDE-22466 URL: https://issues.jboss.org/browse/JBIDE-22466 Project: Tools (JBoss Tools) Issue Type: Task Components: server Reporter: Fred Bricon [~tmader] made some PR on servers depending on Java 8 language features/API, but the server plugins are targeting Java 6. Their BREE should be bumped to JavaSE-1.8 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3887) Include Docker & Vagrant tooling 2.0.0 in JBT 4.4 & DS 10

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3887?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3887. ----------------------------- Verified with JBT 4.4.0.Alpha3 and devstudio 10.0.0.Alpha3. > Include Docker & Vagrant tooling 2.0.0 in JBT 4.4 & DS 10 > --------------------------------------------------------- > > Key: JBDS-3887 > URL: https://issues.jboss.org/browse/JBDS-3887 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: installer, updatesite > Affects Versions: 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 10.0.0.Alpha2 > > > Include Docker & Vagrant tooling 2.0.0 in JBoss Tools 4.4 & DS 10... somehow. (Mechanism to be clarified below.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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