July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22683) OpenShift Explorer: Manage project context menu item is missing in context menu of a connection

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22683?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22683: -------------------------------- Fix Version/s: 4.4.1.AM1 Story Points: 1 > OpenShift Explorer: Manage project context menu item is missing in context menu of a connection > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-22683 > URL: https://issues.jboss.org/browse/JBIDE-22683 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: explorer, openshift_v3 > Fix For: 4.4.1.AM1 > > > I have not spotted any JIRA related to this so I guess it's a bug. We had a context menu item for managing projects in context menu of an OpenShift 3 connection. Now in nightly build of devstudio 10.0.1.AM1 I don't have this context menu item anymore in the context menu of a connection. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22683) OpenShift Explorer: Manage project context menu item is missing in context menu of a connection

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22683?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22683: -------------------------------- Sprint: devex #116 June 2016 > OpenShift Explorer: Manage project context menu item is missing in context menu of a connection > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-22683 > URL: https://issues.jboss.org/browse/JBIDE-22683 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: explorer, openshift_v3 > > I have not spotted any JIRA related to this so I guess it's a bug. We had a context menu item for managing projects in context menu of an OpenShift 3 connection. Now in nightly build of devstudio 10.0.1.AM1 I don't have this context menu item anymore in the context menu of a connection. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

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

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22304?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22304: -------------------------------- Sprint: devex #117 July 2016 (was: devex #116 June 2016) > 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.AM1 > > > 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, 9 months

1
0
0 / 0

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

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22066?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22066: -------------------------------- Sprint: devex #117 July 2016 (was: devex #116 June 2016) > 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.AM1 > > > 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, 9 months

1
0
0 / 0

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

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22239?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22239: -------------------------------- Sprint: devex #117 July 2016 (was: devex #116 June 2016) > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22376) Enable JMX when entering Debug mode

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22376?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22376: -------------------------------- Sprint: devex #117 July 2016 (was: devex #116 June 2016) > Enable JMX when entering Debug mode > ----------------------------------- > > Key: JBIDE-22376 > URL: https://issues.jboss.org/browse/JBIDE-22376 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.1.Beta1 > Reporter: Thomas Mäder > Assignee: Fred Bricon > Fix For: 4.4.1.AM1 > > > We need to update the deployment configuration when entering debug mode. It is not entirely clear how to determine that an Openshift Pod has indeed a wildfly/EAP in it and can be reached with remoting-jmx -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22321) Use Same ServerHotCodeReplaceListener as for local wildfly

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22321?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22321: -------------------------------- Sprint: devex #117 July 2016 (was: devex #116 June 2016) > Use Same ServerHotCodeReplaceListener as for local wildfly > ---------------------------------------------------------- > > Key: JBIDE-22321 > URL: https://issues.jboss.org/browse/JBIDE-22321 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Thomas Mäder > Assignee: Fred Bricon > Fix For: 4.4.x > > > We need to port the fix we have for wildfly to the OpenShiftServer -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22319) Make OpenshiftServer implement IConnectionFacade

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22319?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22319: -------------------------------- Sprint: devex #117 July 2016 (was: devex #116 June 2016) > Make OpenshiftServer implement IConnectionFacade > ------------------------------------------------ > > Key: JBIDE-22319 > URL: https://issues.jboss.org/browse/JBIDE-22319 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Thomas Mäder > Assignee: Fred Bricon > Fix For: 4.4.1.AM1 > > > Add support for having a jmx conection via JBoss remoting to OpenShiftServer. > * need to add jmx client library > * find out the correct url > * configure deployment config with necessary env, ports, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22326) Enable JMX Connections Over "remoting-jmx"

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22326?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22326: -------------------------------- Sprint: devex #117 July 2016 (was: devex #116 June 2016) > Enable JMX Connections Over "remoting-jmx" > ------------------------------------------ > > Key: JBIDE-22326 > URL: https://issues.jboss.org/browse/JBIDE-22326 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jmx > Reporter: Thomas Mäder > Assignee: Fred Bricon > Fix For: 4.4.x > > > Need to add "remoting-jmx" library and support that kind of connection for jmx -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

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

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22261?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22261: -------------------------------- Sprint: (was: devex #116 June 2016) > 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, 9 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 July 2016