May 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23710) Properites: Disable scaling on completed deployments

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23710?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-23710: ---------------------------------------- Assignee: (was: Andre Dietisheim) > Properites: Disable scaling on completed deployments > ---------------------------------------------------- > > Key: JBIDE-23710 > URL: https://issues.jboss.org/browse/JBIDE-23710 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Radim Hopp > Labels: openshift_v3, properties > Fix For: 4.5.0.AM1 > > > In web console, scaling completed deployments is disabled. > In devstudio this option is enabled (in Deployments in Properties View) and after scaling up the completed deployment up (from 0 pods), the pods get scaled, but they are immediately scaled down automatically by openshift. > Sometimes I also got this exception (but not allways): > {noformat} > !ENTRY org.jboss.tools.openshift.ui 4 0 2017-01-10 16:32:41.562 > !MESSAGE Unable to scale wildfly-1 > !STACK 0 > com.openshift.restclient.OpenShiftException: Exception trying to PUT https://10.40.4.205:8443/api/v1/namespaces/testproject/replicationcontrol... response code: 409 Operation cannot be fulfilled on replicationcontrollers "wildfly-1": the object has been modified; please apply your changes to the latest version and try again > at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:114) > at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:65) > at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190) > at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163) > at okhttp3.RealCall.execute(RealCall.java:57) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:217) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:194) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:183) > at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:275) > at org.jboss.tools.openshift.core.connection.Connection.updateResource(Connection.java:451) > at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler$2.run(ScaleDeploymentHandler.java:183) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > I think we should do the same as web console -> disable scaling options on completed deployments. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20569) OpenShift Explorer : "Import Application" menu is confusing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20569?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-20569: ---------------------------------------- Assignee: (was: Andre Dietisheim) > OpenShift Explorer : "Import Application" menu is confusing > ----------------------------------------------------------- > > Key: JBIDE-20569 > URL: https://issues.jboss.org/browse/JBIDE-20569 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Labels: explorer, ux > Fix For: 4.5.0.AM1 > > Attachments: import-application.png > > > [~sspeiche] finds the "Import Application" menu in OpenShift Explorer is confusing: does it mean import from eclipse to openshift or the other way around (it's the latter). Needs better wording. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21372) Server Adapter: automatically create a server for new apps

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21372?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-21372: ---------------------------------------- Assignee: (was: Andre Dietisheim) > Server Adapter: automatically create a server for new apps > ---------------------------------------------------------- > > Key: JBIDE-21372 > URL: https://issues.jboss.org/browse/JBIDE-21372 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.0.AM1 > > > Currently one has to create the OpenShift 3 server adapter manually by using the menu File > New > Server > OpenShift 3 (or context menu in the Server view). We should now also create the server adapter when one successfully finishes the new/import application wizard. To achieve this we'll have to include a page in the new/import-application wizard for the required server settings. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21331) Connection wizard: it looks as if the wizard is creating new connection instances several times

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21331?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-21331: ---------------------------------------- Assignee: (was: Andre Dietisheim) > Connection wizard: it looks as if the wizard is creating new connection instances several times > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-21331 > URL: https://issues.jboss.org/browse/JBIDE-21331 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Priority: Minor > Labels: connection_wizard, openshift_v3 > Fix For: 4.5.0.AM1 > > > The connection wizard creates new connection instances in several places which seems unnecessary (we need it at least once where we dont want to modify an existing connection and operate on a copy before merging the changes back upon successfull verification) > {code:title=ConnctionWizardPageModel} > private void initEditConnection(IConnection connection) { > this.selectedConnection = connection; > this.connection = connection.clone(); > ... > {code} > {code:title=ConnctionWizardPageModel} > public IStatus connect() { > ... > try { > this.connection = createConnection(); > ... > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19181) correct naming of internal packages so that they're consistent across all openshift plugins

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19181?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-19181: ---------------------------------------- Assignee: (was: Andre Dietisheim) > correct naming of internal packages so that they're consistent across all openshift plugins > ------------------------------------------------------------------------------------------- > > Key: JBIDE-19181 > URL: https://issues.jboss.org/browse/JBIDE-19181 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Andre Dietisheim > Fix For: 4.5.0.AM1 > > > Internal packages across the openshift plugins are non-consistent: > ex. > org.jboss.tools.openshift.client: org.jboss.tools.openshift.client.internal > org.jboss.tools.openshift.express.client: org.jboss.tools.openshift.express.client.internal > the base is imho org.jboss.tools.openshift and thus internal packages should always be at org.jboss.tools.openshift.internal across plugins. > For reference, here's the official Eclipse documentation on the topic: http://wiki.eclipse.org/index.php/Naming_Conventions#Java_Packages > {quote} > org.eclipse.jdt.internal.core.compiler - Correct usage > org.eclipse.jdt.core.internal.compiler - Incorrect. internal should immediately follow subproject name. > org.eclipse.core.internal.resources - Correct usage > org.eclipse.internal.core.resources - Incorrect. internal should never immediately follow org.eclipse. > org.eclipse.core.resources.internal - Incorrect. internal should immediately follow Eclipse Platform component name. > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21895) Application wizard: Resource name collisions after deleting and recreating the application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21895?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-21895: ---------------------------------------- Assignee: (was: Andre Dietisheim) > Application wizard: Resource name collisions after deleting and recreating the application > ------------------------------------------------------------------------------------------ > > Key: JBIDE-21895 > URL: https://issues.jboss.org/browse/JBIDE-21895 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Pavol Srna > Labels: application_wizard, openshift_v3 > Fix For: 4.5.0.AM1 > > Attachments: 1st-child-of-project.png, Screen Shot 2016-03-17 at 16.19.05.png, Screenshot 2017-02-02 18.22.34.png, Screenshot 2017-02-02 18.22.43.png, os-resources-empty.png > > > 1) Create e.g. node application in a openshift project > 2) Right click from project explorer -> Delete the application > 3) repeat step 1) > Result: > !Screen Shot 2016-03-17 at 16.19.05.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23924) Properties: display properties for a buildconfig with build type "Binary"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23924?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-23924: ---------------------------------------- Assignee: (was: Andre Dietisheim) > Properties: display properties for a buildconfig with build type "Binary" > ------------------------------------------------------------------------- > > Key: JBIDE-23924 > URL: https://issues.jboss.org/browse/JBIDE-23924 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Aurélien Pupier > Fix For: 4.5.0.AM1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24308) Disable "Import application" contextual menu on build config having no git url configured

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24308?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-24308: ---------------------------------------- Assignee: (was: Andre Dietisheim) > Disable "Import application" contextual menu on build config having no git url configured > ----------------------------------------------------------------------------------------- > > Key: JBIDE-24308 > URL: https://issues.jboss.org/browse/JBIDE-24308 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.4.AM3 > Reporter: Aurélien Pupier > Labels: import_wizard, openshift_v3 > Fix For: 4.5.0.AM1 > > Attachments: image-2017-04-25-15-25-07-634.png, image-2017-04-25-15-25-34-373.png > > > !image-2017-04-25-15-25-07-634.png|thumbnail! > it avoids to have an error dialog just after: > !image-2017-04-25-15-25-34-373.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19412) Cleanup ConnectionURL usage for v3 connections

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19412?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-19412: ---------------------------------------- Assignee: (was: Andre Dietisheim) > Cleanup ConnectionURL usage for v3 connections > ---------------------------------------------- > > Key: JBIDE-19412 > URL: https://issues.jboss.org/browse/JBIDE-19412 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Labels: openshift_v3 > Fix For: 4.5.0.AM1 > > > In ConnectionsRegistry connections are stored by ConnectionURL. ConnectionURL is also used to persist v2 connections. v3 connections on the other hand are persisted in their very own json format. We need to clean this discrepany/inconsistency. We should either only use ConnectionURL for v2 connections or also store v3 connections in the ConnectionURL format. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16512) Some dialogs (and wizards) are not draggable (since they do not have a title bar)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16512?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-16512: ---------------------------------------- Assignee: (was: Andre Dietisheim) > Some dialogs (and wizards) are not draggable (since they do not have a title bar) > --------------------------------------------------------------------------------- > > Key: JBIDE-16512 > URL: https://issues.jboss.org/browse/JBIDE-16512 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Alpha2 > Reporter: Marián Labuda > Priority: Minor > Fix For: 4.5.0.AM1 > > > On Fedora with GNOME many shells (wizards) do not have Title bar and that's the reason they are not dragable / moveable. Before 4.2.0 there was not almost any of the title bars, but with 4.2.0 there is seen improvement. > Specifically these shells do not have title bar: > - Port forwarding (shell opened from application context menu) > - Edit enviroment variables (shell opened from application context menu) > - Import application (wizard opened from application context menu) > - New connection (shell opened from OpenShift explorer view context menu or by click on tool bar button Connect to Openshift) > - Edit connection (shell opened from context menu of connection) > - New domain (shell opened from context menu of connection) > - Edit domain (shell opened from context menu of domain) > - Manage domains (shell opened from context menu of connection) > - New application (wizard open from context menu of connection / domain or File - New - OpenShift Application > Few examples of correct shells: > - Tail Files (shell opened from application context menu) > - Details (shell opened from application context menu) > - Create server adapted (shell opened from application context menu) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 2017