February 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-21793) Zero-click import of CDK

by Pete Muir (JIRA)

Pete Muir created JBIDE-21793: --------------------------------- Summary: Zero-click import of CDK Key: JBIDE-21793 URL: https://issues.jboss.org/browse/JBIDE-21793 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: runtime-detection Reporter: Pete Muir We should try to import the CDK with no-clicks, and hide the detection dialog. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21776) Cannot deploy docker image to OpenShift with manually entered details

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21776?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21776: ------------------------------------------ [~xcoulon] +1 sounds like a good approach > Cannot deploy docker image to OpenShift with manually entered details > --------------------------------------------------------------------- > > Key: JBIDE-21776 > URL: https://issues.jboss.org/browse/JBIDE-21776 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Xavier Coulon > Priority: Critical > Labels: docker, openshift_v3 > Fix For: 4.3.1.CR1 > > Attachments: manually_filled.png, selected_image.png > > > When deploying a docker image to OpenShift it is necessary to fill in namespace and image name at least (repo and tag is optional). Manually entering those values into the Deploy Image to OpenShift wizard does not work, although details are same as those filled automatically via selecting a docker image (click Search... button and select a specific one). > There is no error in error log. > Manually filled in details screenshot: > !manually_filled.png! > Automatically filled details via selecting a specific image screenshot: > !selected_image.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21776) Cannot deploy docker image to OpenShift with manually entered details

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21776?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-21776: --------------------------------------- also, after a deeper look into the code: should we trigger an image pull when the user clicks on 'next' after the first page, if the image does not exist in the selected Docker daemon ? This might be a long-running operation, but it seems required to be able to display the data in the next steps. > Cannot deploy docker image to OpenShift with manually entered details > --------------------------------------------------------------------- > > Key: JBIDE-21776 > URL: https://issues.jboss.org/browse/JBIDE-21776 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Xavier Coulon > Priority: Critical > Labels: docker, openshift_v3 > Fix For: 4.3.1.CR1 > > Attachments: manually_filled.png, selected_image.png > > > When deploying a docker image to OpenShift it is necessary to fill in namespace and image name at least (repo and tag is optional). Manually entering those values into the Deploy Image to OpenShift wizard does not work, although details are same as those filled automatically via selecting a docker image (click Search... button and select a specific one). > There is no error in error log. > Manually filled in details screenshot: > !manually_filled.png! > Automatically filled details via selecting a specific image screenshot: > !selected_image.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21761) Port mapping validation is not correct

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21761?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-21761: --------------------------------------- Services can target a named port on the pod. https://github.com/kubernetes/kubernetes/blob/master/docs/user-guide/serv... . > Port mapping validation is not correct > -------------------------------------- > > Key: JBIDE-21761 > URL: https://issues.jboss.org/browse/JBIDE-21761 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: docker, openshift_v3 > Fix For: 4.3.1.CR1 > > Attachments: validation_msg.png > > > In Deploy docker image on the page with port mapping when adding a new port mapping there is a validation error telling that correct format of pod is alphanumeric, what is wrong. See following image. > !validation_msg.png! > There should be allowed only numbers in range 0-65535. It is not only validation message but it allows to create also mapping to port e.g. "abc123" what should not be possible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21776) Cannot deploy docker image to OpenShift with manually entered details

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21776?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-21776: --------------------------------------- So, in order to fix this issue, the image validator will trigger a search on Docker Hub if no image with the given name exists in the selected Docker daemon (in its local cache). If the image exists on Docker Hub, a warning message will be displayed on the wizard to indicate that the image will have to be pulled first. If no match was found, an error message will be displayed (there is nothing at the moment, which is confusing). [~adietish], [~fbricon], [~mlabuda], are you ok with this ? > Cannot deploy docker image to OpenShift with manually entered details > --------------------------------------------------------------------- > > Key: JBIDE-21776 > URL: https://issues.jboss.org/browse/JBIDE-21776 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Xavier Coulon > Priority: Critical > Labels: docker, openshift_v3 > Fix For: 4.3.1.CR1 > > Attachments: manually_filled.png, selected_image.png > > > When deploying a docker image to OpenShift it is necessary to fill in namespace and image name at least (repo and tag is optional). Manually entering those values into the Deploy Image to OpenShift wizard does not work, although details are same as those filled automatically via selecting a docker image (click Search... button and select a specific one). > There is no error in error log. > Manually filled in details screenshot: > !manually_filled.png! > Automatically filled details via selecting a specific image screenshot: > !selected_image.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21716) Don't re-prompt for password

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21716?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21716: ------------------------------------- If Pete prioritizes this as blocker and believes Max's solution is secure enough for him, then I'm fine passing in via environment variables. [~dgolovin] let's talk to pick a key. is this doable for cr1? [~pmuir] - please confirm environment variable on first start after installation is secure enough for you. > Don't re-prompt for password > ---------------------------- > > Key: JBIDE-21716 > URL: https://issues.jboss.org/browse/JBIDE-21716 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Reporter: Pete Muir > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > > Having installed JBDS and CDK from the installer, and entered your password there, you get re-prompted for your password for the customer portal. This is a poor user experience. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21791) Forge addon - Changing the current file may cause a "file has changed in file vs memory" issue in Eclipse

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21791?page=com.atlassian.jira.plugi... ] George Gastaldi reassigned JBIDE-21791: --------------------------------------- Assignee: (was: George Gastaldi) > Forge addon - Changing the current file may cause a "file has changed in file vs memory" issue in Eclipse > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21791 > URL: https://issues.jboss.org/browse/JBIDE-21791 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.3.1.Beta2 > Reporter: Claus Ibsen > Fix For: 4.3.1.CR1 > > Attachments: eclipse-add.png > > > Similar problem as FORGE-2605 but this time its in Eclipse. > See the attached screenshot, where I have edited the file camel-context.xml, and then run my forge command, which would insert a Camel endpoint at the cursor position. But eclipse has detected a file conflict as in that dialog. > I wonder if the fix should be like in IDEA to save the file before the command is run. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21792) Domain in New OpenShift 2 server adapter wizard are not ordered alphanumerically

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21792?page=com.atlassian.jira.plugi... ] Marián Labuda reassigned JBIDE-21792: ------------------------------------- Assignee: Marián Labuda > Domain in New OpenShift 2 server adapter wizard are not ordered alphanumerically > -------------------------------------------------------------------------------- > > Key: JBIDE-21792 > URL: https://issues.jboss.org/browse/JBIDE-21792 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Marián Labuda > Labels: openshift_v2, server_adapter_wizard > > Domains listed in a combo in the New OpenShift 2 Server Adapter wizard are currently not order alphabetically or alphanumerically. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21792) Domain in New OpenShift 2 server adapter wizard are not ordered alphanumerically

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21792?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21792: ---------------------------------- Labels: openshift_v2 server_adapter_wizard (was: ) > Domain in New OpenShift 2 server adapter wizard are not ordered alphanumerically > -------------------------------------------------------------------------------- > > Key: JBIDE-21792 > URL: https://issues.jboss.org/browse/JBIDE-21792 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Marián Labuda > Labels: openshift_v2, server_adapter_wizard > > Domains listed in a combo in the New OpenShift 2 Server Adapter wizard are currently not order alphabetically or alphanumerically. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21792) Server Adapter Wizard: OpenShift 2 domains are not ordered alphanumerically

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21792?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21792: ---------------------------------- Summary: Server Adapter Wizard: OpenShift 2 domains are not ordered alphanumerically (was: Domain in New OpenShift 2 server adapter wizard are not ordered alphanumerically) > Server Adapter Wizard: OpenShift 2 domains are not ordered alphanumerically > --------------------------------------------------------------------------- > > Key: JBIDE-21792 > URL: https://issues.jboss.org/browse/JBIDE-21792 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Marián Labuda > Labels: openshift_v2, server_adapter_wizard > > Domains listed in a combo in the New OpenShift 2 Server Adapter wizard are currently not order alphabetically or alphanumerically. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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 February 2016