May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19506) Connection wizard, Connection: should have unit tests

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19506?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19506: ------------------------------------- Remaining Estimate: 2 days (was: 1 day) > Connection wizard, Connection: should have unit tests > ------------------------------------------------------ > > Key: JBIDE-19506 > URL: https://issues.jboss.org/browse/JBIDE-19506 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, tests > Fix For: 4.4.0.Alpha3 > > Original Estimate: 2 days > Time Spent: 2 days > Remaining Estimate: 2 days > > In the new implementation of the connection wizard, that allows v2 and v3 connections (JBIDE-19096) we have rather complex behaviour that we should assert via unit tests. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19506) Connection wizard, Connection: should have unit tests

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19506?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19506: ------------------------------------- Remaining Estimate: 1 day (was: 0 minutes) > Connection wizard, Connection: should have unit tests > ------------------------------------------------------ > > Key: JBIDE-19506 > URL: https://issues.jboss.org/browse/JBIDE-19506 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, tests > Fix For: 4.4.0.Alpha3 > > Original Estimate: 2 days > Time Spent: 2 days > Remaining Estimate: 1 day > > In the new implementation of the connection wizard, that allows v2 and v3 connections (JBIDE-19096) we have rather complex behaviour that we should assert via unit tests. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19506) Connection wizard: should have unit tests

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19506?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19506: ------------------------------------------ quite a few more tests added in [#1199h|ttps://github.com/jbosstools/jbosstools-openshift/pull/1199] even though the coverage is still not where I expect it to be in this very crucial part of the tooling. I thus would merge and postpone to add further tests > Connection wizard: should have unit tests > ------------------------------------------ > > Key: JBIDE-19506 > URL: https://issues.jboss.org/browse/JBIDE-19506 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, tests > Fix For: 4.4.0.Alpha3 > > Original Estimate: 2 days > Time Spent: 1 day, 5 hours > Remaining Estimate: 3 hours > > In the new implementation of the connection wizard, that allows v2 and v3 connections (JBIDE-19096) we have rather complex behaviour that we should assert via unit tests. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19506) Connection wizard, Connection: should have unit tests

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19506?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19506: ------------------------------------- Summary: Connection wizard, Connection: should have unit tests (was: Connection wizard: should have unit tests ) > Connection wizard, Connection: should have unit tests > ------------------------------------------------------ > > Key: JBIDE-19506 > URL: https://issues.jboss.org/browse/JBIDE-19506 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, tests > Fix For: 4.4.0.Alpha3 > > Original Estimate: 2 days > Time Spent: 1 day, 5 hours > Remaining Estimate: 3 hours > > In the new implementation of the connection wizard, that allows v2 and v3 connections (JBIDE-19096) we have rather complex behaviour that we should assert via unit tests. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-233) Dialog for adding a new Docker registry account has no title [EBZ#495074]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-233: --------------------------------------- Summary: Dialog for adding a new Docker registry account has no title [EBZ#495074] Key: ERT-233 URL: https://issues.jboss.org/browse/ERT-233 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot Not sure this is compliant with Eclipse UI guidelines -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-234) Editing a Docker registry account requires user to retype the password [EBZ#495075]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-234: --------------------------------------- Summary: Editing a Docker registry account requires user to retype the password [EBZ#495075] Key: ERT-234 URL: https://issues.jboss.org/browse/ERT-234 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot When editing a Docker registry account, the OK button is enabled only if the password field is not empty. As the previous password value has not been retrieved, the user must retype it -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-235) Docker registry account allows for non URL server address [EBZ#495076]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-235: --------------------------------------- Summary: Docker registry account allows for non URL server address [EBZ#495076] Key: ERT-235 URL: https://issues.jboss.org/browse/ERT-235 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot When creating/editing Docker registry accounts, the server address seems rather open instead of URL. Maybe a check on the syntax could be valuable -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-230) Registry accounts does not accept data with _ [EBZ#495070]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-230: --------------------------------------- Summary: Registry accounts does not accept data with _ [EBZ#495070] Key: ERT-230 URL: https://issues.jboss.org/browse/ERT-230 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-231) Registry accounts does not accept data with _ [EBZ#495072]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-231: --------------------------------------- Summary: Registry accounts does not accept data with _ [EBZ#495072] Key: ERT-231 URL: https://issues.jboss.org/browse/ERT-231 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot If you configure a docker registry account with hostname=hub_1.docker.com user=a email=b(a)b.com password=c then close the preference dialog and reopen it, then address is now hub, username 1.docker.com and email a. If you configure a docker registry account with hostname=hub.docker.com user=a_1 email=b(a)b.com password=c then close the preference dialog and reopen it, then address is now hub.docker.com, username a and email 1. If you configure a docker registry account with hostname=hub.docker.com user=a email=b_1(a)b.com password=c then close the preference dialog and reopen it, then address is now hub.docker.com, username a and email b. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-232) Image name validator doesn't accept image repositories with multiple / in them [EBZ#495073]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-232: --------------------------------------- Summary: Image name validator doesn't accept image repositories with multiple / in them [EBZ#495073] Key: ERT-232 URL: https://issues.jboss.org/browse/ERT-232 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot Fix For: Neon (4.6) The following valid image name: docker.io/ibmiccm/rhel71:latest because the repo has multiple forward slashes in it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 May 2016