[JBoss JIRA] (JBIDE-22694) Environment Var Wizard: Improve deletion of environment variables
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22694?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22694:
-----------------------------------
Fix Version/s: 4.4.x
(was: 4.4.1.Final)
> Environment Var Wizard: Improve deletion of environment variables
> -----------------------------------------------------------------
>
> Key: JBIDE-22694
> URL: https://issues.jboss.org/browse/JBIDE-22694
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.1.AM1
> Reporter: Marián Labuda
> Labels: env_var_wizard, openshift_v3
> Fix For: 4.4.x
>
>
> Deletion of environment variable does not match user expectation. If I delete an environment variable which has been added in earlier opened and closed Env. Var wizard, this variable has prefix [deleted]. I don't think this is good practice, we should be consistent across all wizards and dialog, so once user select an env var in table and push Delete button, value should be removed from the table. No labelling should be done here, the table should reflect real current state of environment variable (what it is gonna look like once I hit Finish button).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22805) Add Scale... menus on Pod resources
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22805?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22805:
-----------------------------------
Sprint: devex #119 August 2016 (was: devex #119 August 2016, devex #120 September 2016)
> Add Scale... menus on Pod resources
> -----------------------------------
>
> Key: JBIDE-22805
> URL: https://issues.jboss.org/browse/JBIDE-22805
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.1.AM1
> Reporter: Fred Bricon
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.x
>
>
> I'm regularly confused/frustrated to not find the Scale... menus on the running pods. Each time I need to slap myself in the face to remind me I need to go to the Service level.
> I think it'd be more intuitive if the scale menus were present on the running pods (not on the build ones).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22805) Add Scale... menus on Pod resources
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22805?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22805:
-----------------------------------
Fix Version/s: 4.4.x
(was: 4.4.1.Final)
> Add Scale... menus on Pod resources
> -----------------------------------
>
> Key: JBIDE-22805
> URL: https://issues.jboss.org/browse/JBIDE-22805
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.1.AM1
> Reporter: Fred Bricon
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.x
>
>
> I'm regularly confused/frustrated to not find the Scale... menus on the running pods. Each time I need to slap myself in the face to remind me I need to go to the Service level.
> I think it'd be more intuitive if the scale menus were present on the running pods (not on the build ones).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22818) vagrant service-manager call experiences timeout after output
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22818?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22818:
-----------------------------------
Fix Version/s: 4.4.x
(was: 4.4.1.Final)
> vagrant service-manager call experiences timeout after output
> --------------------------------------------------------------
>
> Key: JBIDE-22818
> URL: https://issues.jboss.org/browse/JBIDE-22818
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.1.AM2
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.4.x
>
>
> {noformat}
> !ENTRY org.jboss.tools.openshift.cdk.server 4 0 2016-07-21 09:48:26.869
> !MESSAGE Unable to successfully complete a call to vagrant service-manager.
> !STACK 0
> java.util.concurrent.TimeoutException: Process output:
> ^[[0m # docker env:^[[0m # Set the following environment variables to enable access to the # docker daemon running inside of the vagrant virtual machine: export DOCKER_HOST=tcp://10.1.2.2:2376 export DOCKER_CERT_PATH='C:\Pedro\Software\Openshift_RHCDK_suite10\cdk\components\rhel\rhel-ose\.vagrant\machines\default\virtualbox\docker\' export DOCKER_TLS_VERIFY=1 export DOCKER_API_VERSION=1.21 ^[[0m^[[0m ^[[0m # openshift env:^[[0m ^[[0m# You can access the OpenShift console on: https://10.1.2.2:8443/console # To use OpenShift CLI, run: oc login https://10.1.2.2:8443 export OPENSHIFT_URL=https://10.1.2.2:8443 export OPENSHIFT_WEB_CONSOLE=https://10.1.2.2:8443/console export DOCKER_REGISTRY=hub.openshift.rhel-cdk.10.1.2.2.xip.io^[[0m ^[[0m # run following command to configure your shell: # eval "$(VAGRANT_NO_COLOR=1 vagrant service-manager env | tr -d '\r')"^[[0m
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:186)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:153)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:108)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:85)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:67)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:59)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.checkOpenShiftHealth(VagrantPoller.java:185)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePing(VagrantPoller.java:174)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePingSafe(VagrantPoller.java:154)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.getCurrentStateSynchronous(VagrantPoller.java:133)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.handleProcessTerminated(CDKLaunchController.java:250)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.access$2(CDKLaunchController.java:242)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController$2.run(CDKLaunchController.java:235)
> !ENTRY org.jboss.tools.openshift.cdk.server 4 0 2016-07-21 09:49:07.139
> !MESSAGE Unable to successfully complete a call to vagrant service-manager.
> !STACK 0
> java.util.concurrent.TimeoutException: Process output:
> ^[[0m # docker env:^[[0m # Set the following environment variables to enable access to the # docker daemon running inside of the vagrant virtual machine: export DOCKER_HOST=tcp://10.1.2.2:2376 export DOCKER_CERT_PATH='C:\Pedro\Software\Openshift_RHCDK_suite10\cdk\components\rhel\rhel-ose\.vagrant\machines\default\virtualbox\docker\' export DOCKER_TLS_VERIFY=1 export DOCKER_API_VERSION=1.21 ^[[0m^[[0m ^[[0m # openshift env:^[[0m ^[[0m# You can access the OpenShift console on: https://10.1.2.2:8443/console # To use OpenShift CLI, run: oc login https://10.1.2.2:8443 export OPENSHIFT_URL=https://10.1.2.2:8443 export OPENSHIFT_WEB_CONSOLE=https://10.1.2.2:8443/console export DOCKER_REGISTRY=hub.openshift.rhel-cdk.10.1.2.2.xip.io^[[0m ^[[0m # run following command to configure your shell: # eval "$(VAGRANT_NO_COLOR=1 vagrant service-manager env | tr -d '\r')"^[[0m
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:186)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:153)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:108)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:85)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:67)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:59)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener.configureFrameworks(ConfigureDependentFrameworksListener.java:53)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener$1.run(ConfigureDependentFrameworksListener.java:43)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22916) Deploy Docker Wizard: Deploying a docker image from OpenShift explorer does not fetch metadata if image is not pulled to a docker connection
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22916?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22916:
-----------------------------------
Fix Version/s: 4.4.2.AM1
(was: 4.4.1.Final)
> Deploy Docker Wizard: Deploying a docker image from OpenShift explorer does not fetch metadata if image is not pulled to a docker connection
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22916
> URL: https://issues.jboss.org/browse/JBIDE-22916
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.2.AM1
>
> Attachments: 2016-09-06 at 14-19-31.mp4
>
>
> When I am trying to deploy a docker image from context menu of a project in OpenShift explorer view and I paste image name (e.g. docker.io/openshift/hello-openshift), image metadata are not fetched/processed and thus there are no environment variables in the wizard and routing (routing wizard page is empty and cannot finish dialog - requires manual entry). This force user to enter the details manually, otherwise he would get deployed not working pod. This is happening only in case when user provide an image without any tag and thus there is/supposed to be assumed tag "latest".
> You can observe that it works when using tag v1.2.1. Difference between images with tag v1.2.1 and latest is that v1.2.1 contains exposed ports also in container config, not just in general config of the image.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23011) Docker Explorer broken on Windows
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23011?page=com.atlassian.jira.plugi... ]
Alexey Kazakov resolved JBIDE-23011.
------------------------------------
Resolution: Done
This is resolved. [~xcoulon] please reopen if I missed anything.
> Docker Explorer broken on Windows
> ---------------------------------
>
> Key: JBIDE-23011
> URL: https://issues.jboss.org/browse/JBIDE-23011
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker
> Affects Versions: 4.4.1.AM3
> Reporter: Martin Malina
> Assignee: Xavier Coulon
> Priority: Critical
> Fix For: 4.4.1.Final
>
> Attachments: docker-explorer.jpg, jbide23011.png, jbide23011_2.png
>
>
> [reply] [−] Description Martin Malina CLA Friend 2016-08-16 08:51:31 EDT
> Created attachment 263612 [details]
> Broken Docker Explorer view
> I just installed a brand new installation of Red Hat JBoss Developer Studio 10.1.0.AM3 which contains Docker Tooling 2.1.0.201608101805 on Windows and when I open Docker Explorer, it contains a red X and "Failed to create the part's controls". Also, there is a button that says Details > >.
> There is this NPE in the error log view:
> {code}
> java.lang.NullPointerException
> at org.eclipse.linuxtools.docker.core.DockerConnectionManager.reloadConnections(DockerConnectionManager.java:63)
> at org.eclipse.linuxtools.docker.core.DockerConnectionManager.<init>(DockerConnectionManager.java:50)
> at org.eclipse.linuxtools.docker.core.DockerConnectionManager.getInstance(DockerConnectionManager.java:44)
> at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerView.getInitialInput(DockerExplorerView.java:93)
> at org.eclipse.ui.navigator.CommonNavigator.createPartControl(CommonNavigator.java:206)
> at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerView.createConnectionsPane(DockerExplorerView.java:195)
> at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerView.createPartControl(DockerExplorerView.java:147)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:151)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityView.createPartControl(CompatibilityView.java:143)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:341)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54)
> at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:966)
> at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:931)
> at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:151)
> at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:375)
> at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:294)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:105)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:74)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:56)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:129)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:975)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:651)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$1.run(PartRenderingEngine.java:536)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:520)
> at org.eclipse.e4.ui.workbench.renderers.swt.ElementReferenceRenderer.createWidget(ElementReferenceRenderer.java:70)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:975)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:651)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:757)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:728)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:722)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:706)
> at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer.showTab(StackRenderer.java:1317)
> at org.eclipse.e4.ui.workbench.renderers.swt.LazyStackRenderer$1.handleEvent(LazyStackRenderer.java:72)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:40)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:233)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:145)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:4813)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:211)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:36)
> at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:201)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135)
> at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78)
> at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39)
> at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:94)
> at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:60)
> at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374)
> at org.eclipse.e4.ui.model.application.ui.impl.ElementContainerImpl.setSelectedElement(ElementContainerImpl.java:173)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.showElementInWindow(ModelServiceImpl.java:617)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:581)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.delegateBringToTop(PartServiceImpl.java:770)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:744)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:682)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:677)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1205)
> at org.eclipse.ui.internal.WorkbenchPage.showPart(WorkbenchPage.java:1283)
> at org.eclipse.ui.internal.WorkbenchPage.busyShowView(WorkbenchPage.java:1274)
> at org.eclipse.ui.internal.WorkbenchPage$12.run(WorkbenchPage.java:4316)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchPage.showView(WorkbenchPage.java:4312)
> at org.eclipse.ui.internal.WorkbenchPage.showView(WorkbenchPage.java:4292)
> at org.eclipse.ui.internal.quickaccess.ViewElement.execute(ViewElement.java:77)
> at org.eclipse.ui.internal.quickaccess.SearchField$2.handleElementSelected(SearchField.java:200)
> at org.eclipse.ui.internal.quickaccess.QuickAccessContents.handleSelection(QuickAccessContents.java:507)
> at org.eclipse.ui.internal.quickaccess.QuickAccessContents.access$0(QuickAccessContents.java:497)
> at org.eclipse.ui.internal.quickaccess.QuickAccessContents$1.keyPressed(QuickAccessContents.java:542)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:168)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4410)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1103)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1088)
> at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1130)
> at org.eclipse.swt.widgets.Text.sendKeyEvent(Text.java:1789)
> at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1126)
> at org.eclipse.swt.widgets.Widget.wmChar(Widget.java:1547)
> at org.eclipse.swt.widgets.Control.WM_CHAR(Control.java:4910)
> at org.eclipse.swt.widgets.Text.WM_CHAR(Text.java:2722)
> at org.eclipse.swt.widgets.Control.windowProc(Control.java:4791)
> at org.eclipse.swt.widgets.Text.windowProc(Text.java:2704)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5102)
> at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
> at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2552)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3814)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
> 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(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> 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)
> {code}
> This is a tracking issue for this upstream BZ: https://bugs.eclipse.org/bugs/show_bug.cgi?id=499745
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23033) Sprint Planning Script
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23033?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-23033:
-----------------------------------
Fix Version/s: 4.4.x
(was: 4.4.1.Final)
> Sprint Planning Script
> ----------------------
>
> Key: JBIDE-23033
> URL: https://issues.jboss.org/browse/JBIDE-23033
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: upstream
> Affects Versions: 4.4.1.AM3
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.4.x
>
>
> A script for the sprint planning meeting should be made. This script should help facilitate the following goals:
> 1) Devs should give a general idea of the main issues they are targeting for the sprint
> 2) Devs should indicate if they are fully booked with top-priority issues, or can bump some for others who need help
> 3) Devs should indicate if they have critical or major issues that need help that are not targeted to this sprint
> 4) QE, having more experience using the tools every day for months in both clean and dirty workspaces, should act partly as a project owner
> 4a) QE should list what they perceive as the most troublesome or annoying issues for the component they test (or other components)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months