June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21857) Hot class reload doesn't work on OpenShift

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21857: ----------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Final) > Hot class reload doesn't work on OpenShift > ------------------------------------------ > > Key: JBIDE-21857 > URL: https://issues.jboss.org/browse/JBIDE-21857 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.4.x > > Attachments: HCRFailure.zip > > > When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will : > - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync > - will always fail if a method signature changed, the debugger saying JDK is out of sync > Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server) > This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

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

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21828?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21828: ----------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Final) > 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: Thomas Mäder > Fix For: 4.4.x > > 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22198) Sometimes validation for required parameter in Template Parameters wizard page when creating an application is not available

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22198?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22198: ----------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Final) > Sometimes validation for required parameter in Template Parameters wizard page when creating an application is not available > ---------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22198 > URL: https://issues.jboss.org/browse/JBIDE-22198 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Aurélien Pupier > Fix For: 4.4.x > > Attachments: screenshot-1.png > > > Having a validation, forbidding to go to next page and click finish will provide more guidance to user and avoid him an error dialog when clicking finish -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22066) Server adapter: Stopping debugging of OpenShift application should get application back to normal state.

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22066?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22066: ----------------------------------- Fix Version/s: 4.4.1.Alpha1 (was: 4.4.0.Final) > Server adapter: Stopping debugging of OpenShift application should get application back to normal state. > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22066 > URL: https://issues.jboss.org/browse/JBIDE-22066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: openshift_v3, server_adapter > Fix For: 4.4.1.Alpha1 > > > When user stop or delete Server Adapter where debugging has been enabled, application should be able to get back to normal state - remove environment variable for debugging and remove ports for debugging from deployment config. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21969) Show in Browser: route chooser should allow to user to choose route permanently

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21969?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21969: ----------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Final) > Show in Browser: route chooser should allow to user to choose route permanently > ------------------------------------------------------------------------------- > > Key: JBIDE-21969 > URL: https://issues.jboss.org/browse/JBIDE-21969 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Andre Dietisheim > Assignee: Viacheslav Kabanovich > Labels: openshift_v3, server_adapter > Fix For: 4.4.x > > Attachments: route-chooser.png > > > steps to reproduce: > # ASSERT: have an apps with service and route running on OpenShift. Have it imported to your workspace > # ASSERT: you need at least a 2nd route in the same project (ex. by having a 2nd app in the same project) > # EXEC: launch New OpenShift 3 Server Adapter wizard > # ASSERT: make sure that you have *Prompt for route when multiple routes available to show in browser* checked (no route permanently selected) > # EXEC: create the adapter by picking service, local project etc. > # EXEC: in the context menu of your new server adapter: pick Show In > Web Browser > # ASSERT: Route chooser shows up (since there are several routes available) > Result: > There's no way to permanently choose a route. The route chooser will always show up (as long as I have several routes in the same project) > !route-chooser.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

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

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22239?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22239: ----------------------------------- Fix Version/s: 4.4.1.Alpha1 (was: 4.4.0.Final) > 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.Alpha1 > > > 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22231) Ensure OpenShift and Docker tooling support the MSA workflow

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22231?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22231: ----------------------------------- Fix Version/s: 4.4.1.Alpha1 (was: 4.4.0.Final) > Ensure OpenShift and Docker tooling support the MSA workflow > ------------------------------------------------------------ > > Key: JBIDE-22231 > URL: https://issues.jboss.org/browse/JBIDE-22231 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: docker, openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.4.1.Alpha1 > > > This Epic gather the issues we've identified that currently prevent [~burrsutter] to perform his MSA demo entirely from Eclipse -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22304) Server Editor: Pod deployment path is not shown

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22304?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22304: ----------------------------------- Fix Version/s: 4.4.1.Alpha1 (was: 4.4.0.Final) > Server Editor: Pod deployment path is not shown > ----------------------------------------------- > > Key: JBIDE-22304 > URL: https://issues.jboss.org/browse/JBIDE-22304 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: openshift_v3, server_editor > Fix For: 4.4.1.Alpha1 > > > In Server Adapter wizard is not shown Pod deployment path. Widget supposed to display the path is empty. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22261) Server Adapter: "Show in > Server Log" should open the current running pod log

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22261?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22261: ----------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Final) > Server Adapter: "Show in > Server Log" should open the current running pod log > ------------------------------------------------------------------------------ > > Key: JBIDE-22261 > URL: https://issues.jboss.org/browse/JBIDE-22261 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Final > Reporter: Fred Bricon > Assignee: Viacheslav Kabanovich > Fix For: 4.4.x > > > It's currently not practical to open the log for the running server adapter. Users need to open the pod log from the OpenShift Explorer. > Instead, "Show in > Server Log" should open the current running pod log, from the OpenShift 3 Server adapter, in the Servers view. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22243) Properties: "Refresh" has no effect

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22243?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22243: ----------------------------------- Fix Version/s: 4.4.1.Alpha1 (was: 4.4.0.Final) > Properties: "Refresh" has no effect > ----------------------------------- > > Key: JBIDE-22243 > URL: https://issues.jboss.org/browse/JBIDE-22243 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Fix For: 4.4.1.Alpha1 > > Attachments: refreshing-wont-help.ogv > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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