June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21744) cdk-created docker connection can have wrong name if you have multiple cdk server adapters

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21744?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21744: -------------------------------- Sprint: devex #116 June 2016 > cdk-created docker connection can have wrong name if you have multiple cdk server adapters > ------------------------------------------------------------------------------------------ > > Key: JBIDE-21744 > URL: https://issues.jboss.org/browse/JBIDE-21744 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.x > > > I noticed that if I have two cdk server adapters, start the first one, stop it, start the second, then docker explorer will only show a connection of the first server name, not the second. > This is probably because the connection will stay there after the first server start and on second server start, the tooling only checks if the docker host url matches. If it does, it will just reuse it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21744) cdk-created docker connection can have wrong name if you have multiple cdk server adapters

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21744?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21744: -------------------------------- Story Points: 6 > cdk-created docker connection can have wrong name if you have multiple cdk server adapters > ------------------------------------------------------------------------------------------ > > Key: JBIDE-21744 > URL: https://issues.jboss.org/browse/JBIDE-21744 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.x > > > I noticed that if I have two cdk server adapters, start the first one, stop it, start the second, then docker explorer will only show a connection of the first server name, not the second. > This is probably because the connection will stay there after the first server start and on second server start, the tooling only checks if the docker host url matches. If it does, it will just reuse it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19812) Refactor IConnection to be agnostic of authorization specifics

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19812?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-19812: --------------------------------------- probably worth downgrading the severity. > Refactor IConnection to be agnostic of authorization specifics > -------------------------------------------------------------- > > Key: JBIDE-19812 > URL: https://issues.jboss.org/browse/JBIDE-19812 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Labels: openshift_v3 > Fix For: 4.4.x > > > The auth scheme can change in v3. A plain IConnection should be able to be refactored to support the auth details as an interface and details like get/set password, username, etc should be moved to those interface implementations. > {code} > public interface IConnection { > ... > public String getUsername(); > public void setUsername(String username); > public String getPassword(); > public void setPassword(String password); > public void setRememberPassword(boolean rememberPassword); > > public boolean isRememberPassword(); > ... > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20036) As I user I want to be able to add image streams to my project

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20036?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-20036: --------------------------------------- You are correct, pushing and image to the registry now creates an IS. This could be useful if our image lives in an external registry but its probably worth down grading or even closing this issue until we have more demand. > As I user I want to be able to add image streams to my project > -------------------------------------------------------------- > > Key: JBIDE-20036 > URL: https://issues.jboss.org/browse/JBIDE-20036 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Labels: openshift_v3 > Fix For: 4.4.x > > > When creating a new application via templates I am required to have the docker images (base builder image etc.) to be available. Otherwise the build wont succeed. > You can see this in the instrcutions for the eap templates where the steps to create an app via those templates are 2: create the image streams & create the app via the templates: > https://github.com/adietish/application-templates/blob/master/README.md > {code} > $ osc create -n yourproject -f jboss-image-streams.json > $ osc process -n yourproject -f eap/eap6-basic-sti.json -v APPLICATION_NAME=helloworld,APPLICATION_HOSTNAME=helloworld.yourproject.l... | osc create -n yourproject -f - > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22277) Connection wizard: Auto guess Openshift connections

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22277?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22277: ------------------------------------- Summary: Connection wizard: Auto guess Openshift connections (was: Auto guess Openshift connections) > Connection wizard: Auto guess Openshift connections > --------------------------------------------------- > > Key: JBIDE-22277 > URL: https://issues.jboss.org/browse/JBIDE-22277 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff MAURY > Priority: Minor > Labels: connection_wizard, new_and_noteworthy, openshift_v3 > Fix For: 4.4.x > > > When creating a new Openshift connection, it would be possible to provide default values for the differents fields by looking at the $HOME/.kube/config YAML files that stores various Openshift installations the user has been connected to through the Openshift oc client. > The same feature exists in the Docker tooling so this might be interesting to have the same at the Openshift side. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22277) Connection wizard: Auto guess Openshift connections

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22277?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22277: ------------------------------------- Labels: connection_wizard new_and_noteworthy openshift_v3 (was: new_and_noteworthy openshift_v3) > Connection wizard: Auto guess Openshift connections > --------------------------------------------------- > > Key: JBIDE-22277 > URL: https://issues.jboss.org/browse/JBIDE-22277 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff MAURY > Priority: Minor > Labels: connection_wizard, new_and_noteworthy, openshift_v3 > Fix For: 4.4.x > > > When creating a new Openshift connection, it would be possible to provide default values for the differents fields by looking at the $HOME/.kube/config YAML files that stores various Openshift installations the user has been connected to through the Openshift oc client. > The same feature exists in the Docker tooling so this might be interesting to have the same at the Openshift side. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22277) Auto guess Openshift connections

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22277?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22277: ------------------------------------- Story Points: 4 > Auto guess Openshift connections > -------------------------------- > > Key: JBIDE-22277 > URL: https://issues.jboss.org/browse/JBIDE-22277 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff MAURY > Priority: Minor > Labels: connection_wizard, new_and_noteworthy, openshift_v3 > Fix For: 4.4.x > > > When creating a new Openshift connection, it would be possible to provide default values for the differents fields by looking at the $HOME/.kube/config YAML files that stores various Openshift installations the user has been connected to through the Openshift oc client. > The same feature exists in the Docker tooling so this might be interesting to have the same at the Openshift side. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19812) Refactor IConnection to be agnostic of authorization specifics

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19812?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19812: ------------------------------------- Story Points: 16 > Refactor IConnection to be agnostic of authorization specifics > -------------------------------------------------------------- > > Key: JBIDE-19812 > URL: https://issues.jboss.org/browse/JBIDE-19812 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Labels: openshift_v3 > Fix For: 4.4.x > > > The auth scheme can change in v3. A plain IConnection should be able to be refactored to support the auth details as an interface and details like get/set password, username, etc should be moved to those interface implementations. > {code} > public interface IConnection { > ... > public String getUsername(); > public void setUsername(String username); > public String getPassword(); > public void setPassword(String password); > public void setRememberPassword(boolean rememberPassword); > > public boolean isRememberPassword(); > ... > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19960) Import wizard: Should be able to specify "Working set" when importing project

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19960?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19960: ------------------------------------- Story Points: 4 (was: 84) > Import wizard: Should be able to specify "Working set" when importing project > ----------------------------------------------------------------------------- > > Key: JBIDE-19960 > URL: https://issues.jboss.org/browse/JBIDE-19960 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Priority: Minor > Labels: import_wizard, openshift_v3 > Fix For: 4.4.x > > > # ASSERT: make sure that you have package explorer set to display working sets and "Other Projects" disabled (unchecked) > # EXEC: launch import wizard > # EXEC: check if you can see you project once the import is finished. > Result: > You cannot spot your project since it was imported to "Other Projects" which is disabled. > We should allow users to specify a working set when importing a new project via Import wizard. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19960) Import wizard: Should be able to specify "Working set" when importing project

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19960?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19960: ------------------------------------- Story Points: 8 > Import wizard: Should be able to specify "Working set" when importing project > ----------------------------------------------------------------------------- > > Key: JBIDE-19960 > URL: https://issues.jboss.org/browse/JBIDE-19960 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Priority: Minor > Labels: import_wizard, openshift_v3 > Fix For: 4.4.x > > > # ASSERT: make sure that you have package explorer set to display working sets and "Other Projects" disabled (unchecked) > # EXEC: launch import wizard > # EXEC: check if you can see you project once the import is finished. > Result: > You cannot spot your project since it was imported to "Other Projects" which is disabled. > We should allow users to specify a working set when importing a new project via Import wizard. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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