May 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25109) Server adapter editor: provide ability to only change debug port (and not the debug port key)

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25109?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-25109: ---------------------------------- Assignee: Dmitrii Bocharov (was: Andre Dietisheim) > Server adapter editor: provide ability to only change debug port (and not the debug port key) > --------------------------------------------------------------------------------------------- > > Key: JBIDE-25109 > URL: https://issues.jboss.org/browse/JBIDE-25109 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.1.AM2 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: openshift_v3, server_adapter_editor > Fix For: 4.6.x > > > Currently there's only 1 checkbox to allow the user to set the debugging key and port. If one only wants to set a custom debug port only, he cannot, he also has to provide the debug key at the same time. We should provide an additional checkbox to enable the debug port only, changing the existing one to only enable/disable the debug key. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25109) Server adapter editor: provide ability to only change debug port (and not the debug port key)

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25109?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25109: ------------------------------- Sprint: devex #149 May 2018 > Server adapter editor: provide ability to only change debug port (and not the debug port key) > --------------------------------------------------------------------------------------------- > > Key: JBIDE-25109 > URL: https://issues.jboss.org/browse/JBIDE-25109 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.1.AM2 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: openshift_v3, server_adapter_editor > Fix For: 4.6.x > > > Currently there's only 1 checkbox to allow the user to set the debugging key and port. If one only wants to set a custom debug port only, he cannot, he also has to provide the debug key at the same time. We should provide an additional checkbox to enable the debug port only, changing the existing one to only enable/disable the debug key. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25509) Properties: one can not select multiple resources

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25509?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25509: ------------------------------- Sprint: devex #146 March 2018, devex #147 April 2018 (was: devex #146 March 2018, devex #147 April 2018, devex #149 May 2018) > Properties: one can not select multiple resources > ------------------------------------------------- > > Key: JBIDE-25509 > URL: https://issues.jboss.org/browse/JBIDE-25509 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.2.AM2 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: properties > Fix For: 4.6.x > > > steps: > # ASSERT: have an OpenShift app running > # EXEC: in OpenShift explorer: select the project and open up the "Properties" view. In the properties view select "Pods" > # ASSERT: there are multiple pods listed > # EXEC: try to select several ones (ex. in order to delete them) > Result: > You can only select a single entry, you cannot select several ones and ex. delete them at once. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25509) Properties: one can not select multiple resources

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25509?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25509: ------------------------------- Sprint: devex #146 March 2018, devex #147 April 2018, devex #149 May 2018 (was: devex #146 March 2018, devex #147 April 2018) > Properties: one can not select multiple resources > ------------------------------------------------- > > Key: JBIDE-25509 > URL: https://issues.jboss.org/browse/JBIDE-25509 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.2.AM2 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: properties > Fix For: 4.6.x > > > steps: > # ASSERT: have an OpenShift app running > # EXEC: in OpenShift explorer: select the project and open up the "Properties" view. In the properties view select "Pods" > # ASSERT: there are multiple pods listed > # EXEC: try to select several ones (ex. in order to delete them) > Result: > You can only select a single entry, you cannot select several ones and ex. delete them at once. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25905) [Deploy Image to OpenShift ->Service & Routing Settings] Service Port table awkward behavior after reset

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25905?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25905: ------------------------------- Sprint: devex #149 May 2018 > [Deploy Image to OpenShift ->Service & Routing Settings] Service Port table awkward behavior after reset > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-25905 > URL: https://issues.jboss.org/browse/JBIDE-25905 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.3.AM3 > Reporter: Denis Golovin > Assignee: Andre Dietisheim > Fix For: 4.6.x > > Attachments: service-ports.gif, services-routing-page-no-labels.png, services-routing-page.png > > > [Service & Routing Settings] page in [Deploy Image to OpenShift] Wizard. > Service Ports table starts to behave awkward after reset. > steps: > # ASSERT: have a docker image available that exposes several ports (ex. registry.access.redhat.com/openshift3/ose-haproxy-router:v3.7.14 which exposes 4 ports) > # EXEC: in Docker Explorer: select your docker image and pick "Deploy to OpenShift..." from the context menu > # ASSERT: "Deploy Image to OpenShift" wizard shows up > # EXEC: get to the "Services & Routing Settings" page > # ASSERT: all ports are listed, a port is checked in column "Used by route" > !services-routing-page.png! > # EXEC: hit "Reset" (and confirm the dialog that asks you if you want to reset the ports) > # EXEC: click in the column "Used by route" on the 2nd port (or any unchecked entry) > Result: > Labels for columns "Name", "Service Port", "Pod Port" disappear > !services-routing-page-no-labels.png! > !service-ports.gif! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25995) Update Minishift's container runtime versions available in jboss-stack

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25995?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-25995: ---------------------------------- Sprint: devex #149 May 2018 > Update Minishift's container runtime versions available in jboss-stack > ---------------------------------------------------------------------- > > Key: JBIDE-25995 > URL: https://issues.jboss.org/browse/JBIDE-25995 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk > Affects Versions: 4.6.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Fix For: 4.6.0.AM1 > > > Add missing minishift verions (1.15.1, 1.16, 1.16.1 not all necessarily) into minishift.yaml file to be available in runtime download wizard under Minishift 1.7+ server adapter. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25995) Update Minishift's container runtime versions available in jboss-stack

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25995?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-25995: ---------------------------------- Story Points: 3 > Update Minishift's container runtime versions available in jboss-stack > ---------------------------------------------------------------------- > > Key: JBIDE-25995 > URL: https://issues.jboss.org/browse/JBIDE-25995 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk > Affects Versions: 4.6.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Fix For: 4.6.0.AM1 > > > Add missing minishift verions (1.15.1, 1.16, 1.16.1 not all necessarily) into minishift.yaml file to be available in runtime download wizard under Minishift 1.7+ server adapter. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25677) Server adapter: Timers are incorrectly managed

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25677?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25677: ------------------------------------- Fix Version/s: 4.6.0.AM2 (was: 4.6.0.AM1) > Server adapter: Timers are incorrectly managed > ---------------------------------------------- > > Key: JBIDE-25677 > URL: https://issues.jboss.org/browse/JBIDE-25677 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: openshift, openshift_v3, server_adapter > Fix For: 4.6.0.AM2 > > > Timers are incorrectly managed in OpenShift server adapter. I tried to create a NodeJS server adapter on OpenShift Online Starter. As the first rsync is long (thanks to .npm and node_modules), it may take more than 5mns as OpenShift Online Starter is resource limited. I think we should rather monitor the activity of the rsync operation (through messages) and set a timer related to this activity. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25504) Support hot deploy for workspace dependencies for SpringBoot applications on OpenShift

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25504?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25504: ------------------------------------- Fix Version/s: 4.6.0.AM2 (was: 4.6.0.AM1) > Support hot deploy for workspace dependencies for SpringBoot applications on OpenShift > -------------------------------------------------------------------------------------- > > Key: JBIDE-25504 > URL: https://issues.jboss.org/browse/JBIDE-25504 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.2.AM2 > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: openshift, openshift_v3, server_adapter > Fix For: 4.6.0.AM2 > > Attachments: springboot-dependencies.zip > > > When a SpringBoot application is being deployed on OpenShift with the server adapter, we should support the following use case: > * the SpringBoot app has a dependency which is avalailable in the workspace > * when a modifiction is done on the dependency code, it should be synced to OpenShift by the server adapter -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25838) Explorer: expand connection to the level that it was expanded to after editing it

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25838?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-25838: ------------------------------------- Sprint: devex #149 May 2018 > Explorer: expand connection to the level that it was expanded to after editing it > --------------------------------------------------------------------------------- > > Key: JBIDE-25838 > URL: https://issues.jboss.org/browse/JBIDE-25838 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.2.AM3 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: connection, explorer > Fix For: 4.6.0.AM1 > > > steps: > # ASSERT: in OpenShift Explorer: have a connection that is expanded to at least show a/all the projects > # EXEC: edit the connection, change the url, hit "Finish" > Result: > Connection is updated (refreshed) but collapsed, wont show the/all the projects > Expected result: > Connection is updated (refreshed) and expanded like it was before editing it, showing the project(s) (and even service(s) if it was expanded to that level before editing it) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2018