October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23371) Deploy image wizard: "Services and Routing Settings" page needs to explain to user what the settings result in.

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23371?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23371: ------------------------------------- Attachment: services-and-routing-page.png > Deploy image wizard: "Services and Routing Settings" page needs to explain to user what the settings result in. > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23371 > URL: https://issues.jboss.org/browse/JBIDE-23371 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Andre Dietisheim > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM3 > > Attachments: services-and-routing-page.png > > > steps to reproduce: > # EXEC: In Docker Explroer: pick an image and choose "Deploy to OpenShift..." in the context menu > # EXEC: get to the "Services & Routing Settings" page > Result: > !services-and-routing-page.png! > The page allows to add/remove/edit ports and to configure a route. It's not obvious to the user what these settings are for and what they result in being created (a single service and route are created). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23372) Resource wizard: lots of empty space to the right of the project settings

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-23372: ---------------------------------------- Summary: Resource wizard: lots of empty space to the right of the project settings Key: JBIDE-23372 URL: https://issues.jboss.org/browse/JBIDE-23372 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.4.1.AM2 Reporter: Andre Dietisheim In wizard to create new resources the 1st line that allows one to select the OpenShift project, there's plenty of space to the right. The project combo should be sclaed to use all the available horizontal space so that the widgets are nicely aligned !empty-horiz-space.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23030) Scaling a service changes the wrong deployment

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23030?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23030: ------------------------------------- Fix Version/s: 4.4.2.AM3 > Scaling a service changes the wrong deployment > ---------------------------------------------- > > Key: JBIDE-23030 > URL: https://issues.jboss.org/browse/JBIDE-23030 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Priority: Critical > Fix For: 4.4.2.AM3 > > > In openshift explorer, when scaling a service that has 2 deployments, it deploys pod from the oldest deployment instead of the latest. Eventually, these pods are killed by openshift. > The workaround is to open the properties view and issue a scale command on a deployment directly. > However, because scaling is such a front-and-center feature from the explorer, I believe it's critical we fix it ASAP -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23030) Scaling a service changes the wrong deployment

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23030?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23030: ------------------------------------------ [~jcantrill] could you please add steps so that I and QE can verify this? > Scaling a service changes the wrong deployment > ---------------------------------------------- > > Key: JBIDE-23030 > URL: https://issues.jboss.org/browse/JBIDE-23030 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Priority: Critical > Fix For: 4.4.2.AM3 > > > In openshift explorer, when scaling a service that has 2 deployments, it deploys pod from the oldest deployment instead of the latest. Eventually, these pods are killed by openshift. > The workaround is to open the properties view and issue a scale command on a deployment directly. > However, because scaling is such a front-and-center feature from the explorer, I believe it's critical we fix it ASAP -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23306) Application wizard: Provide increased "Details" panel size

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23306?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23306: ------------------------------------- Summary: Application wizard: Provide increased "Details" panel size (was: Provide increased "Details" panel size) > Application wizard: Provide increased "Details" panel size > ---------------------------------------------------------- > > Key: JBIDE-23306 > URL: https://issues.jboss.org/browse/JBIDE-23306 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Aurélien Pupier > Labels: application_wizard, openshift_v3 > Fix For: 4.4.x > > Attachments: screenshot-1.png > > > Currently, it provides a 2 lines and half visibility. > 2 things: > - perhaps we can add enough space for mor elines, 4? > - if we can avoid to cut the 3rd line (not sure that it is easy as it might be dependent on font?) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23306) Application wizard: Provide increased "Details" panel size

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23306?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23306: ------------------------------------- Labels: application_wizard openshift_v3 (was: ) > Application wizard: Provide increased "Details" panel size > ---------------------------------------------------------- > > Key: JBIDE-23306 > URL: https://issues.jboss.org/browse/JBIDE-23306 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Aurélien Pupier > Labels: application_wizard, openshift_v3 > Fix For: 4.4.x > > Attachments: screenshot-1.png > > > Currently, it provides a 2 lines and half visibility. > 2 things: > - perhaps we can add enough space for mor elines, 4? > - if we can avoid to cut the 3rd line (not sure that it is easy as it might be dependent on font?) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23306) Application wizard: Provide increased "Details" panel size

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23306?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23306: ------------------------------------- Fix Version/s: 4.4.x > Application wizard: Provide increased "Details" panel size > ---------------------------------------------------------- > > Key: JBIDE-23306 > URL: https://issues.jboss.org/browse/JBIDE-23306 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Aurélien Pupier > Labels: application_wizard, openshift_v3 > Fix For: 4.4.x > > Attachments: screenshot-1.png > > > Currently, it provides a 2 lines and half visibility. > 2 things: > - perhaps we can add enough space for mor elines, 4? > - if we can avoid to cut the 3rd line (not sure that it is easy as it might be dependent on font?) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4119) Some paths are too long for the uninstaller

by Jan Richter (JIRA)

Jan Richter created JBDS-4119: --------------------------------- Summary: Some paths are too long for the uninstaller Key: JBDS-4119 URL: https://issues.jboss.org/browse/JBDS-4119 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: platform-installer Affects Versions: 10.2.0.AM2 Reporter: Jan Richter Assignee: Jan Richter Fix For: 10.2.0.AM3 It is possible to install everything and still get 'path too long' error on uninstallation. For example it seems that drive labels are in fact factored into the 255 character path limit in powershell. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-642) Add regression test for FUSETOOLS-1726

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-642?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík updated JBTIS-642: ------------------------------- Original Estimate: 2 hours Remaining Estimate: 2 hours > Add regression test for FUSETOOLS-1726 > -------------------------------------- > > Key: JBTIS-642 > URL: https://issues.jboss.org/browse/JBTIS-642 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.0.0 > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Fix For: 4.3.0.Final > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > SSIA -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22598) Support runtime detection for manual CDK install

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22598?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22598. --------------------------------- It works correctly for me now. Verified in devstudio-10.2.0.AM2-v20161014-1657-B6205-installer-standalone.jar > Support runtime detection for manual CDK install > ------------------------------------------------ > > Key: JBIDE-22598 > URL: https://issues.jboss.org/browse/JBIDE-22598 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk, runtime-detection > Affects Versions: 4.4.0.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.2.AM2 > > > Right now with CDK 2.1 when you have a manual cdk install (i.e. using cdk.zip and then adding the vagrant box yourself), there will be no .cdk marker, so Runtime Detection will not work. > The only case where Runtime Detection will work is when you use the (as of now Windows-only) suite installer. At that point Runtime Detection will do its thing silently without you noticing. > The way I see it there are two options: > a) Create and upstream issue with CDK and ask them to include a basic .cdk in their zip > b) Make the runtime detection work without .cdk -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 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 October 2016