June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18665) Application wizard: Should not use project-name as application name if it's invalid, should sanitze it

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18665?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-18665: ---------------------------------- Comment: was deleted (was: Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER.) > Application wizard: Should not use project-name as application name if it's invalid, should sanitze it > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18665 > URL: https://issues.jboss.org/browse/JBIDE-18665 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.CR2 > Reporter: Andre Dietisheim > Assignee: Marián Labuda > Priority: Minor > Labels: application_wizard > Fix For: LATER > > Attachments: non-alphanumeric-application-name.png > > > In JBIDE-18052 we started using the project name as suggested application name. If the project name is using non-alphanumeric characters, the suggested application name is invalid. We should not suggest invalid application names, we should sanitize those names before suggesting those. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18665) Application wizard: Should not use project-name as application name if it's invalid, should sanitze it

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18665?page=com.atlassian.jira.plugi... ] Marián Labuda reassigned JBIDE-18665: ------------------------------------- Resolution: (was: Won't Fix) Assignee: Marián Labuda > Application wizard: Should not use project-name as application name if it's invalid, should sanitze it > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18665 > URL: https://issues.jboss.org/browse/JBIDE-18665 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.CR2 > Reporter: Andre Dietisheim > Assignee: Marián Labuda > Priority: Minor > Labels: application_wizard > Fix For: LATER > > Attachments: non-alphanumeric-application-name.png > > > In JBIDE-18052 we started using the project name as suggested application name. If the project name is using non-alphanumeric characters, the suggested application name is invalid. We should not suggest invalid application names, we should sanitize those names before suggesting those. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20156) Connection wizard: when opened from "JBoss Central" it's inconsistent with when opened from "OpenShift Explorer"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20156?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-20156 at 6/26/15 7:57 AM: ------------------------------------------------------------------- [~deshuai] I cant reproduce this with your steps. For me New->Connection from explorer (or via button in the ruler of the explorer view) always deafults to an OpenShift v2 server type while your screenshots show you having a v3 type. Did you choose this manually? Are we missing this step in the description? In the result that you have and expect I dont fully understand whats the extent of the inconsistency: Is it that in [^login-1.png] you have authentication defaulting to "Basic" while its set to token in [^login-2.png]? Can you please elaborate on what exactly is inconsistent for you? {quote} 1. Open the login dialog from "JBoss Central" {quote} How? Via icon in the ruler or via context menu New->Connection? Did you switch the default type "OpenShift v2" to "OpenShift v3"? {quote} Expect result: The login dialog should be consistent. Actual result: The login dialog of openshift is inconsistent. {quote} What exactly is inconsistent? The authentication type "Basic"/"Token"? was (Author: adietish): [~deshuai] I cant reproduce this with your steps. For me New->Connection from explorer (or via button in the ruler of the explorer view) always deafults to an OpenShift v2 server type while your screenshots show you having a v3 type. Did you choose this manually? Are we missing this step in the description? In the result that you have and expect I dont fully understand whats the extent of the inconsistency: Is it that in [^login-1.png] you have authentication defaulting to "Basic" while its set to token in [^login-2.png]? Can you please elaborate on what exactly is inconsistent for you? > Connection wizard: when opened from "JBoss Central" it's inconsistent with when opened from "OpenShift Explorer" > ---------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20156 > URL: https://issues.jboss.org/browse/JBIDE-20156 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Ma Deshuai > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard, openshift_v3 > Fix For: 4.3.0.Beta2 > > Attachments: login-1.png, login-2.png > > > OpenShift plug version: > 3.0.0.Beta2-v20150623-1035-B854 > Steps: > 1. Open the login dialog from "JBoss Central" > 2. Open the login dialog from "OpenShift Explorer" > Expect result: > The login dialog should be consistent. > Actual result: > The login dialog of openshift is inconsistent. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20156) Connection wizard: when opened from "JBoss Central" it's inconsistent with when opened from "OpenShift Explorer"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20156?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20156: ------------------------------------- Summary: Connection wizard: when opened from "JBoss Central" it's inconsistent with when opened from "OpenShift Explorer" (was: The login dialog opened from "JBoss Central" is inconsistent with the one opened from "OpenShift Explorer") > Connection wizard: when opened from "JBoss Central" it's inconsistent with when opened from "OpenShift Explorer" > ---------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20156 > URL: https://issues.jboss.org/browse/JBIDE-20156 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Ma Deshuai > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard, openshift_v3 > Fix For: 4.3.0.Beta2 > > Attachments: login-1.png, login-2.png > > > OpenShift plug version: > 3.0.0.Beta2-v20150623-1035-B854 > Steps: > 1. Open the login dialog from "JBoss Central" > 2. Open the login dialog from "OpenShift Explorer" > Expect result: > The login dialog should be consistent. > Actual result: > The login dialog of openshift is inconsistent. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20156) The login dialog opened from "JBoss Central" is inconsistent with the one opened from "OpenShift Explorer"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20156?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-20156: ---------------------------------------- Assignee: Andre Dietisheim > The login dialog opened from "JBoss Central" is inconsistent with the one opened from "OpenShift Explorer" > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20156 > URL: https://issues.jboss.org/browse/JBIDE-20156 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Ma Deshuai > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard, openshift_v3 > Fix For: 4.3.0.Beta2 > > Attachments: login-1.png, login-2.png > > > OpenShift plug version: > 3.0.0.Beta2-v20150623-1035-B854 > Steps: > 1. Open the login dialog from "JBoss Central" > 2. Open the login dialog from "OpenShift Explorer" > Expect result: > The login dialog should be consistent. > Actual result: > The login dialog of openshift is inconsistent. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20156) The login dialog opened from "JBoss Central" is inconsistent with the one opened from "OpenShift Explorer"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20156?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20156: ------------------------------------- Labels: connection_wizard (was: ) > The login dialog opened from "JBoss Central" is inconsistent with the one opened from "OpenShift Explorer" > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20156 > URL: https://issues.jboss.org/browse/JBIDE-20156 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Ma Deshuai > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard, openshift_v3 > Fix For: 4.3.0.Beta2 > > Attachments: login-1.png, login-2.png > > > OpenShift plug version: > 3.0.0.Beta2-v20150623-1035-B854 > Steps: > 1. Open the login dialog from "JBoss Central" > 2. Open the login dialog from "OpenShift Explorer" > Expect result: > The login dialog should be consistent. > Actual result: > The login dialog of openshift is inconsistent. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20156) The login dialog opened from "JBoss Central" is inconsistent with the one opened from "OpenShift Explorer"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20156?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20156: ------------------------------------- Labels: connection_wizard openshift_v3 (was: connection_wizard) > The login dialog opened from "JBoss Central" is inconsistent with the one opened from "OpenShift Explorer" > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20156 > URL: https://issues.jboss.org/browse/JBIDE-20156 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Ma Deshuai > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard, openshift_v3 > Fix For: 4.3.0.Beta2 > > Attachments: login-1.png, login-2.png > > > OpenShift plug version: > 3.0.0.Beta2-v20150623-1035-B854 > Steps: > 1. Open the login dialog from "JBoss Central" > 2. Open the login dialog from "OpenShift Explorer" > Expect result: > The login dialog should be consistent. > Actual result: > The login dialog of openshift is inconsistent. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20156) The login dialog opened from "JBoss Central" is inconsistent with the one opened from "OpenShift Explorer"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20156?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-20156 at 6/26/15 7:52 AM: ------------------------------------------------------------------- [~deshuai] I cant reproduce this with your steps. For me New->Connection from explorer (or via button in the ruler of the explorer view) always deafults to an OpenShift v2 server type while your screenshots show you having a v3 type. Did you choose this manually? Are we missing this step in the description? In the result that you have and expect I dont fully understand whats the extent of the inconsistency: Is it that in [^login-1.png] you have authentication defaulting to "Basic" while its set to token in [login-2.png]? Can you please elaborate on what exactly is inconsistent for you? was (Author: adietish): [~deshuai] I cant reproduce this with your steps. For me New->Connection from explorer (or via button in the ruler of the explorer view) always deafults to an OpenShift v2 server type while your screenshots show you having a v3 type. Did you choose this manually? Are we missing this step in the description? > The login dialog opened from "JBoss Central" is inconsistent with the one opened from "OpenShift Explorer" > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20156 > URL: https://issues.jboss.org/browse/JBIDE-20156 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Ma Deshuai > Priority: Minor > Fix For: 4.3.0.Beta2 > > Attachments: login-1.png, login-2.png > > > OpenShift plug version: > 3.0.0.Beta2-v20150623-1035-B854 > Steps: > 1. Open the login dialog from "JBoss Central" > 2. Open the login dialog from "OpenShift Explorer" > Expect result: > The login dialog should be consistent. > Actual result: > The login dialog of openshift is inconsistent. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20156) The login dialog opened from "JBoss Central" is inconsistent with the one opened from "OpenShift Explorer"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20156?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-20156 at 6/26/15 7:52 AM: ------------------------------------------------------------------- [~deshuai] I cant reproduce this with your steps. For me New->Connection from explorer (or via button in the ruler of the explorer view) always deafults to an OpenShift v2 server type while your screenshots show you having a v3 type. Did you choose this manually? Are we missing this step in the description? In the result that you have and expect I dont fully understand whats the extent of the inconsistency: Is it that in [^login-1.png] you have authentication defaulting to "Basic" while its set to token in [^login-2.png]? Can you please elaborate on what exactly is inconsistent for you? was (Author: adietish): [~deshuai] I cant reproduce this with your steps. For me New->Connection from explorer (or via button in the ruler of the explorer view) always deafults to an OpenShift v2 server type while your screenshots show you having a v3 type. Did you choose this manually? Are we missing this step in the description? In the result that you have and expect I dont fully understand whats the extent of the inconsistency: Is it that in [^login-1.png] you have authentication defaulting to "Basic" while its set to token in [login-2.png]? Can you please elaborate on what exactly is inconsistent for you? > The login dialog opened from "JBoss Central" is inconsistent with the one opened from "OpenShift Explorer" > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20156 > URL: https://issues.jboss.org/browse/JBIDE-20156 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Ma Deshuai > Priority: Minor > Fix For: 4.3.0.Beta2 > > Attachments: login-1.png, login-2.png > > > OpenShift plug version: > 3.0.0.Beta2-v20150623-1035-B854 > Steps: > 1. Open the login dialog from "JBoss Central" > 2. Open the login dialog from "OpenShift Explorer" > Expect result: > The login dialog should be consistent. > Actual result: > The login dialog of openshift is inconsistent. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20156) The login dialog opened from "JBoss Central" is inconsistent with the one opened from "OpenShift Explorer"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20156?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20156: ------------------------------------------ [~deshuai] I cant reproduce this with your steps. For me New->Connection from explorer (or via button in the ruler of the explorer view) always deafults to an OpenShift v2 server type while your screenshots show you having a v3 type. Did you choose this manually? Are we missing this step in the description? > The login dialog opened from "JBoss Central" is inconsistent with the one opened from "OpenShift Explorer" > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20156 > URL: https://issues.jboss.org/browse/JBIDE-20156 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Ma Deshuai > Priority: Minor > Fix For: 4.3.0.Beta2 > > Attachments: login-1.png, login-2.png > > > OpenShift plug version: > 3.0.0.Beta2-v20150623-1035-B854 > Steps: > 1. Open the login dialog from "JBoss Central" > 2. Open the login dialog from "OpenShift Explorer" > Expect result: > The login dialog should be consistent. > Actual result: > The login dialog of openshift is inconsistent. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 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 2015