April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20937) Create resource(s) from json

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20937?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20937: ------------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > Create resource(s) from json > ---------------------------- > > Key: JBIDE-20937 > URL: https://issues.jboss.org/browse/JBIDE-20937 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR2 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.4.0.Alpha2 > > Attachments: New Resource Wizard Mockup.bmml, New Resource Wizard Mockup.png > > > It would be nice to have feature to create a new resource, e.g. image stream or pod, from provided json. Similar to "oc create -f some_resource.json" > Currently it would be very usable for MW application templates, because jboss-eap basic s2i template requires image stream which is defined in another json. Also there are applications which are consisting of separately defined resources (e.g. in openshift origin repo is hello world application and its having defined pod in separated json). > This could be available via context menu New - Resource (like we have for application, projects and connections). And it could be accessible via context menu of a project and specific resource type (e.g. for tree item Image Streams). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21668) Fix collection setters in ResourcesUIModel

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21668?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21668: ------------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha1) > Fix collection setters in ResourcesUIModel > ------------------------------------------ > > Key: JBIDE-21668 > URL: https://issues.jboss.org/browse/JBIDE-21668 > 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.x > > > Created as follow up to JBIDE-21590. > Collections setters in ResourcesUIModel, for instance > {code} > public void setBuildConfigs(Collection<IResourceUIModel> buildConfigs) { > firePropertyChange(PROP_BUILD_CONFIGS, resources.get(ResourceKind.BUILD_CONFIG), resources.put(ResourceKind.BUILD_CONFIG, new ArrayList<>(buildConfigs))); > } > {code} > fire incorrect newValue object, because java.util.Map.put(key, value) returns old object associated with the key, not the one just set. > At this moment, this does not create any bugs, because these setters are still not used, all changes go through ResourcesUIModel.add, ResourcesUIModel.remove, ResourcesUIModel.update that have correct notification. But bugs may appear as soon as collection setters are used, so that they better be fixed, for instance this way : > {code} > public void setBuildConfigs(Collection<IResourceUIModel> buildConfigs) { > setResourcesForKind(buildConfigs, ResourceKind.BUILD_CONFIG); > } > private void setResourcesForKind(Collection<IResourceUIModel> list, String kind) { > List<IResourceUIModel> oldList = resources.get(kind); > List<IResourceUIModel> newList = new ArrayList<IResourceUIModel>(list); > resources.put(kind, newList); > firePropertyChange(getProperty(kind), oldList, newList); > } > {code} > and with use of private setResourcesForKind all other setters will remain one-liners. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21420) Delete more OpenShift projects at once

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21420?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21420: ------------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha1) > Delete more OpenShift projects at once > -------------------------------------- > > Key: JBIDE-21420 > URL: https://issues.jboss.org/browse/JBIDE-21420 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: explorer, openshift_v3 > Fix For: 4.4.x > > > It would be nice to remove more projects at once. Currently I can only delete project by project by selecting and choosing delete in its context menu. I would like to select more projects and choose Delete project(s)... in theirs context menu as it is similar for OpenShift 2 domains. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21121) Port Forwarding: Warning/error dialog should pop up if there is no oc binary when opening Port forwarding dialog

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21121?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21121: ------------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > Port Forwarding: Warning/error dialog should pop up if there is no oc binary when opening Port forwarding dialog > ---------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21121 > URL: https://issues.jboss.org/browse/JBIDE-21121 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.4.0.Alpha2 > > > OpenShift 3 port forwarding features requires 'oc' binary to be set up in tooling. It's done in Workbench preference dialog on page OpenShift 3. If there is no 'oc' binary set and user invokes a port forwarding dialog, it is opened and even Start All button is enabled. User finds out that it is not possible to perform only when he gets an error message upon clicking on Start All button describing the problem. There could be some warning/error dialog popped up before opening a port forwarding dialog if there is no 'oc' location set in preferences. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21068) Project wizard: Set maximum length for display name

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21068?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21068: ------------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > Project wizard: Set maximum length for display name > --------------------------------------------------- > > Key: JBIDE-21068 > URL: https://issues.jboss.org/browse/JBIDE-21068 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jan Richter > Priority: Minor > Labels: openshift_v3, project_wizard > Fix For: 4.4.0.Alpha2 > > > Currently the 'Display Name' text field has no length limit. OpenShift on the other hand will only allow fields of length up to 65536 characters. Would be nice to let the user only input a valid length string. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21828) OpenShift Explorer view flickers when refreshing a service

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21828?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21828: ------------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > OpenShift Explorer view flickers when refreshing a service > ---------------------------------------------------------- > > Key: JBIDE-21828 > URL: https://issues.jboss.org/browse/JBIDE-21828 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Jeff Cantrill > Fix For: 4.4.0.Alpha2 > > Attachments: Screenshot 2016-03-08 10.32.39.png > > > When calling the "Refresh" command on a service, the tree view flickers because of too many refresh calls. > Adding some traces revealed 25 calls to {{BaseExplorerContentProvider#refreshViewer(Object)}}, which seems way too much for a service with a single pod. > Attachement: screenshot of the OpenShift Server view, showing 2 projects, one of which has 3 services. > Custom/added logs in the console: > {code} > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/mongodb > Refreshing viewer from sample/mongodb > Refreshing viewer from sample/mongodb > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21818) Too large margins in wizards

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21818?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21818: ------------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > Too large margins in wizards > ---------------------------- > > Key: JBIDE-21818 > URL: https://issues.jboss.org/browse/JBIDE-21818 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Priority: Minor > Labels: openshift_v3 > Fix For: 4.4.0.Alpha2 > > Attachments: Screenshot 2016-03-04 11.19.59.png > > > Some wizard have too large margins, wasting space and making them inconsistent with the other Eclipse wizards in general. > See attached screenshot as an example -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21755) Properties: "Eager-er" loading of the project properties

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21755?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21755: ------------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > Properties: "Eager-er" loading of the project properties > -------------------------------------------------------- > > Key: JBIDE-21755 > URL: https://issues.jboss.org/browse/JBIDE-21755 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Priority: Minor > Labels: openshift_v3, properties > Fix For: 4.4.0.Alpha2 > > > Once I logged in the OpenShift Explorer, if I expand the connection and select my project, all tables on the tabbed properties view are empty. I need to expand the project in the OpenShift Explorer view to trigger a loading which then allows for displaying the data in the properties view. This is somehow confusing because the user may think that the OpenShift project is empty. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21871) Weird message in error log when connecting to cdk openshift - Unauthorized

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21871?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21871: ------------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha1) > Weird message in error log when connecting to cdk openshift - Unauthorized > --------------------------------------------------------------------------- > > Key: JBIDE-21871 > URL: https://issues.jboss.org/browse/JBIDE-21871 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Martin Malina > Fix For: 4.4.x > > Attachments: secure-storage.png > > > Everytime I start cdk and then want to connect to the openshift instance in OpenShift Explorer view, I get this info message in Error Log: > Unauthorized. Trying to reauthenticate > All the time I was thinking that the connection is actually not working, but then I tried to create a project and it worked. > I can see a few issues here: > 1. Why is this info message displayed even though the connection is actually established? It's confusing. > 2. There is no clear indication if a connection is established or not - could we do something about it? If there is an existing project, then you can see it. But currently there is none for the openshift-dev user by default. What makes is worse is the fact that once you start cdk, there is a little arrow next to the openshift connection as if you could expand it. When you do that, it will expand 1 line with "Loading.." and then it will suddenly disappear, so it really looks like something is wrong. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21885) Remove "()" from context-menu name of Start Build

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21885?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-21885. -------------------------------------- Resolution: Rejected Rejecting as we cannot reproduce this. [~xiazhao2015] please feel free to reopen if you still experience this issue. > Remove "()" from context-menu name of Start Build > -------------------------------------------------- > > Key: JBIDE-21885 > URL: https://issues.jboss.org/browse/JBIDE-21885 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Environment: JBoss OpenShift 3 Tools 3.2.0.Alpha1-v20160316-2139-B1202 > OS: Fedora 22 & Windows 10 > Reporter: Xia Zhao > Assignee: Andre Dietisheim > Priority: Minor > Labels: openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: build-config-properties-menu.png > > > The "()" from context-menu name of Start Build should be removed -- 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