June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22676) Context menu Server Adapter of a service in properties view does not work

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-22676: ------------------------------------- Summary: Context menu Server Adapter of a service in properties view does not work Key: JBIDE-22676 URL: https://issues.jboss.org/browse/JBIDE-22676 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.0.Final Reporter: Marián Labuda When I have selected a project with an applicaiton in OpenShift Explorer view, I can handle the service also in properties view. But context menu item "Server Adapter..." in context menu of the service in properties view does nothing. No wizard is opened, nor any error in error log is shown. Context menu item in OpenShift explorer works ok. Only the one in properties view is affected. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22676) Context menu Server Adapter of a service in properties view does not work

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22676?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22676: ---------------------------------- Labels: openshift_v3 (was: ) > Context menu Server Adapter of a service in properties view does not work > ------------------------------------------------------------------------- > > Key: JBIDE-22676 > URL: https://issues.jboss.org/browse/JBIDE-22676 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Labels: openshift_v3 > > When I have selected a project with an applicaiton in OpenShift Explorer view, I can handle the service also in properties view. But context menu item "Server Adapter..." in context menu of the service in properties view does nothing. No wizard is opened, nor any error in error log is shown. Context menu item in OpenShift explorer works ok. Only the one in properties view is affected. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22675) Server Adapter Wizard: Wizard opened via OpenShift Explorer does not have title

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22675?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22675: ---------------------------------- Labels: openshift_v server_adapter_wizard (was: ) > Server Adapter Wizard: Wizard opened via OpenShift Explorer does not have title > ------------------------------------------------------------------------------- > > Key: JBIDE-22675 > URL: https://issues.jboss.org/browse/JBIDE-22675 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Priority: Minor > Labels: openshift_v3, server_adapter_wizard > > OpenShift 3 Server adapter wizard opened from context menu of a service in OpenShift Explorer view does not have title. Shell has title "". Server adapter wizard opened via Servers view or through shell menu File - New does have title "New Server" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22675) Server Adapter Wizard: Wizard opened via OpenShift Explorer does not have title

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22675?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22675: ---------------------------------- Labels: openshift_v3 server_adapter_wizard (was: openshift_v server_adapter_wizard) > Server Adapter Wizard: Wizard opened via OpenShift Explorer does not have title > ------------------------------------------------------------------------------- > > Key: JBIDE-22675 > URL: https://issues.jboss.org/browse/JBIDE-22675 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Priority: Minor > Labels: openshift_v3, server_adapter_wizard > > OpenShift 3 Server adapter wizard opened from context menu of a service in OpenShift Explorer view does not have title. Shell has title "". Server adapter wizard opened via Servers view or through shell menu File - New does have title "New Server" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22675) Server Adapter Wizard: Wizard opened via OpenShift Explorer does not have title

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-22675: ------------------------------------- Summary: Server Adapter Wizard: Wizard opened via OpenShift Explorer does not have title Key: JBIDE-22675 URL: https://issues.jboss.org/browse/JBIDE-22675 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.0.Final Reporter: Marián Labuda Priority: Minor OpenShift 3 Server adapter wizard opened from context menu of a service in OpenShift Explorer view does not have title. Shell has title "". Server adapter wizard opened via Servers view or through shell menu File - New does have title "New Server" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22653) Can't scale pods down to 0

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22653?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-22653: ---------------------------------- Assignee: Jeff MAURY > Can't scale pods down to 0 > -------------------------- > > Key: JBIDE-22653 > URL: https://issues.jboss.org/browse/JBIDE-22653 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Fred Bricon > Assignee: Jeff MAURY > Labels: explorer, openshift_v3 > Fix For: 4.4.1.AM2 > > > The scale to... menu lets you scale to any number of replicas, but you can't go down to 0. > The webconsoles allows it, albeit with a big warning: "Are you sure you want to scale deploymentname to 0 replicas? This will stop all pods for the deployment." > My take is we should have the same behavior in eclipse -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22649) When importing an OS2 app, the Git import does not use the default import folder used while importing OS3

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22649?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22649: ------------------------------- Story Points: 2 > When importing an OS2 app, the Git import does not use the default import folder used while importing OS3 > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22649 > URL: https://issues.jboss.org/browse/JBIDE-22649 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Fix For: 4.4.1.AM2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22239) Allow a user to choose to permanently update their desired replicas for their deployment

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22239?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22239: ------------------------------------ Using master, scaling up or down will update both the RC and the DC in my test. Side effect ? > Allow a user to choose to permanently update their desired replicas for their deployment > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22239 > URL: https://issues.jboss.org/browse/JBIDE-22239 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff Cantrill > Assignee: Viacheslav Kabanovich > Labels: openshift_v3 > Fix For: 4.4.1.AM1 > > > When scaling, we should provide an option to a user who is scaling their deployment to update the deploymentconfig desired replias setting. Currently, if you scale the deployment in the explorer view or the replicationcontroller in the tabs view, image or config change triggers from a DC will set the replica count to whats defined their. Suggest: > * Adding a custom dialog in the "..to.." option > * Update to use a spinner > * Add a checkbox to 'make the change perminent' > * If checkbox=true, you should only need to update the dc if it has a configchange trigger. > * Optionally show checkbox if unable to determine the dc associated with the deployment. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-682) Fix bugs in the Guides Test

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/JBTIS-682?page=com.atlassian.jira.plugin.... ] Matej Kralik updated JBTIS-682: ------------------------------- Affects Version/s: (was: 4.2.5.Final) > Fix bugs in the Guides Test > --------------------------- > > Key: JBTIS-682 > URL: https://issues.jboss.org/browse/JBTIS-682 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: QE, teiid > Affects Versions: 4.3.0.Beta1 > Reporter: Matej Kralik > Assignee: Matej Kralik > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22674) Refresh handler throws NPE when no active part are selected

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22674?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22674: ------------------------------------ {code} ENTRY org.eclipse.ui 4 0 2016-06-29 11:10:55.991 !MESSAGE Unhandled event loop exception !STACK 0 org.eclipse.e4.core.di.InjectionException: java.lang.NullPointerException at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:64) at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:282) at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:264) at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:488) at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:433) at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:454) at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem$3.handleEvent(AbstractContributionItem.java:482) 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.Display.runDeferredEvents(Display.java:4228) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3816) 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(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.__invoke(DelegatingMethodAccessorImpl.java:43) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java) at java.lang.reflect.Method.invoke(Method.java:498) 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) Caused by: java.lang.NullPointerException at org.jboss.tools.openshift.internal.ui.handler.RefreshResourceHandler.execute(RefreshResourceHandler.java:39) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295) at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.__invoke(DelegatingMethodAccessorImpl.java:43) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java) at java.lang.reflect.Method.invoke(Method.java:498) at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54) ... 39 more {code} > Refresh handler throws NPE when no active part are selected > ----------------------------------------------------------- > > Key: JBIDE-22674 > URL: https://issues.jboss.org/browse/JBIDE-22674 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Fix For: 4.4.1.AM2 > > > EXEC: start Eclipse but don't select any part > EXEC: unfold an OS3 connection > EXEC: fill the credentials dialog > EXEC: Refresh the OS3 connection > ASSERT: the refresh handler throws NPE in the Eclipse log -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 June 2016