April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22237) Properties: table is not updated when resource is selected and edited

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22237?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-22237: ---------------------------------- Story Points: 3 > Properties: table is not updated when resource is selected and edited > --------------------------------------------------------------------- > > Key: JBIDE-22237 > URL: https://issues.jboss.org/browse/JBIDE-22237 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: openshift_v3, properties > Fix For: 4.4.0.Alpha1 > > Attachments: error-upon-scale-down.png > > > When an entry is selected in a properties tab for an openshift resource and the resources changes, you can no longer edit/update that resource until its refreshed. For example while implementing scaling, I can select a dc, scale it up, but then receive an error when I immediately try to scale it down because the resource version is out of sync. > steps to reproduce: > # ASSERT: make sure that you have at least 1 application in OpenShift > # EXEC: in Explorer: select your service > # EXEC: open up Properties and select "Deployments" tab > # EXEC: pick "Scale > Up" in the context menu > # EXEC: pick "Scale > Down" in the context menu > Result: > An error is popping up telling you that the resource is outdated. > !error-upon-scale-down.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22118) Application wizard: Should support "builder" images

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22118?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-22118: ---------------------------------- Story Points: 25 > Application wizard: Should support "builder" images > --------------------------------------------------- > > Key: JBIDE-22118 > URL: https://issues.jboss.org/browse/JBIDE-22118 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477 > Openshift plugin 3.1.0.Final-v20160401-2357-B263 > Reporter: Rafael Benevides > Assignee: Jeff Cantrill > Fix For: 4.4.0.Alpha1 > > Attachments: buildconfig page.png, page_1.png > > > I installed the following image stream: https://raw.githubusercontent.com/jboss-openshift/application-templates/m... > It contains several "builder" images. I would like to use jboss-eap70-openshift:1.3-Beta to build a JavaEE 7 application available at https://github.com/redhat-helloworld-msa/hello . But the Openshift plugin only shows "templates". > Openshift plugin should support "builder" images. These images contain "builder" on their tags. > Ref: Jan-5-2016 discussion: http://etherpad.corp.redhat.com/OpenShiftAndJBossStudio -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21437) Server adapter: cannot publish, cannot find "oc" executable

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21437?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21437. --------------------------------- Verified in JBDS 10.0.0.Alpha1 B5227. > Server adapter: cannot publish, cannot find "oc" executable > ----------------------------------------------------------- > > Key: JBIDE-21437 > URL: https://issues.jboss.org/browse/JBIDE-21437 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Labels: openshift_v3, server_adapter > Fix For: 4.4.0.Alpha1 > > Attachments: could-not-sync-error.png, oc-binary-preferences.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21988) OpenShift Websocket reconnects on timeout, even when the OpenShift connection is deleted

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21988?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21988. --------------------------------- > OpenShift Websocket reconnects on timeout, even when the OpenShift connection is deleted > ---------------------------------------------------------------------------------------- > > Key: JBIDE-21988 > URL: https://issues.jboss.org/browse/JBIDE-21988 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Labels: openshift_v3 > Fix For: 4.4.0.Alpha1 > > > OpenShift Websocket reconnects on timeout, even when the OpenShift connection is deleted > Is shows in the logs, when running the openshift plugin from source -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 updated JBIDE-22247: ---------------------------------- Description: 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! was: Context menus of OpenShift resources in Properties view are quite messy. It could be ordered better. 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! > 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 > Labels: openshift_v3, properties, ux > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22006) Error is shown when selecting Build Config tabbed property in Properties view

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22006?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22006. --------------------------------- Verified in JBDS 10.0.0.Alpha1 B5227. > Error is shown when selecting Build Config tabbed property in Properties view > ----------------------------------------------------------------------------- > > Key: JBIDE-22006 > URL: https://issues.jboss.org/browse/JBIDE-22006 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Priority: Critical > Labels: openshift_v3, properties > Fix For: 4.4.0.Alpha1 > > > When I am trying to display properties for a build config of an OpenShift 3 application, error is shown with following stack trace: > {code} > java.lang.ClassCastException: com.openshift.internal.restclient.model.build.SourceBuildStrategy cannot be cast to com.openshift.restclient.model.build.ISTIBuildStrategy > at org.jboss.tools.openshift.internal.ui.property.BuildConfigPropertySource.getPropertyValue(BuildConfigPropertySource.java:106) > at org.eclipse.ui.views.properties.PropertySheetEntry.refreshValues(PropertySheetEntry.java:590) > at org.eclipse.ui.views.properties.PropertySheetEntry.refreshChildEntries(PropertySheetEntry.java:547) > at org.eclipse.ui.views.properties.PropertySheetEntry.setValues(PropertySheetEntry.java:736) > at org.eclipse.ui.views.properties.PropertySheetViewer.setInput(PropertySheetViewer.java:986) > at org.eclipse.ui.views.properties.PropertySheetPage.selectionChanged(PropertySheetPage.java:518) > at org.jboss.tools.openshift.internal.ui.property.tabbed.OpenShiftResourcePropertySection$2.selectionChanged(OpenShiftResourcePropertySection.java:135) > 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.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:4481) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430) > 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:498) > 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)

9 years, 11 months

1
0
0 / 0

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

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-22247: ------------------------------------- Summary: 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 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. 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, 11 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 updated JBIDE-22247: ---------------------------------- Labels: openshift_v3 properties ux (was: ) > 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 > Labels: openshift_v3, properties, ux > 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. 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20506) Reorganize context menu items of a OpenShift v3 connection

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20506?page=com.atlassian.jira.plugi... ] Marián Labuda resolved JBIDE-20506. ----------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.4.x) Resolution: Done Set this one as a duplicate issue of JBIDE-22242 which is more complex and cover other context menus too. > Reorganize context menu items of a OpenShift v3 connection > ---------------------------------------------------------- > > Key: JBIDE-20506 > URL: https://issues.jboss.org/browse/JBIDE-20506 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.x > Reporter: Marián Labuda > Assignee: Alexey Kazakov > Priority: Minor > Labels: help_wanted > Fix For: 4.4.0.Alpha1 > > > Menu items of a v3 connection has following order: > {panel} > New > Remove > Edit > --------------- > Manage Project > Show In > ----------------- > Import Application > ----------------- > Show Properties > Refresh > {panel} > we should follow same order as for v2 connection or at least keep consistency in order - at first connection managing related items (New, Edit, Remove), then project related (Manage Project), then "application" related (Show In, Import Application), then specific connection handling (Refresh) and in the end Properties. > Then submenu items of context menu item New... should be in order Connection - (Project -) Application. Not Application - Connection. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22002) Connecting to a OS 3 Server adapter on restarted Eclipse throws error

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22002?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22002. --------------------------------- Verified in JBDS 10.0.0.Alpha1 B5227. > Connecting to a OS 3 Server adapter on restarted Eclipse throws error > --------------------------------------------------------------------- > > Key: JBIDE-22002 > URL: https://issues.jboss.org/browse/JBIDE-22002 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Labels: openshift_v3 > Fix For: 4.4.0.Alpha1 > > > If I am having an OpenShift 3 Server Adapter in Servers view and I restart IDE, I have to fill in credentials again to start OS 3 server adapter. After filling valid credentials using local CDK OS 3.2, following error pops up and server is still stopped. Following attempt to start the server adapter finish successfully (it is because connection is already established, but in first attempt although I was prompted to fill in credentials and connection was some time during the process established, it seems the server adapter was not able to comprehend it. > {code} > The OpenShift service for server eap-app at OpenShift 3 (10.3.2.2) could not be reached. > com.openshift.restclient.authorization.UnauthorizedException: Unauthorized to access resource. You can access the server using Basic authentication. > at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:485) > at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:158) > at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:139) > at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:387) > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:287) > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:276) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.pollState(OpenShiftLaunchController.java:73) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:56) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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