October 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22959) Properties: rename Deployment to Replication Controller

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22959?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-22959. ------------------------------------ > Properties: rename Deployment to Replication Controller > ------------------------------------------------------- > > Key: JBIDE-22959 > URL: https://issues.jboss.org/browse/JBIDE-22959 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: openshift_v3, properties > Fix For: 4.5.1.Final > > > We should rename Deployment in tabbed properties to Replication Controller. I was complaining about it some times ago, but now I found also good reason to change it - underlying Kubernetes technology has Deployment resources and ReplicaSets (new generation of replication controller). And those resources are something a bit different although it has similar functionality. For users coming from Kubernetes world or those who are familiar with Kubernetes, could this be a bit misleading. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22959) Properties: rename Deployment to Replication Controller

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22959?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22959: ------------------------------------------ 1y later the web-ui is still labelling Replication Controllers "Deployments" like we do. Resolving as WONT_FIX > Properties: rename Deployment to Replication Controller > ------------------------------------------------------- > > Key: JBIDE-22959 > URL: https://issues.jboss.org/browse/JBIDE-22959 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: openshift_v3, properties > Fix For: 4.5.1.Final > > > We should rename Deployment in tabbed properties to Replication Controller. I was complaining about it some times ago, but now I found also good reason to change it - underlying Kubernetes technology has Deployment resources and ReplicaSets (new generation of replication controller). And those resources are something a bit different although it has similar functionality. For users coming from Kubernetes world or those who are familiar with Kubernetes, could this be a bit misleading. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22959) Properties: rename Deployment to Replication Controller

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22959?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22959: ------------------------------------- Fix Version/s: 4.5.1.Final (was: 4.5.x) > Properties: rename Deployment to Replication Controller > ------------------------------------------------------- > > Key: JBIDE-22959 > URL: https://issues.jboss.org/browse/JBIDE-22959 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: openshift_v3, properties > Fix For: 4.5.1.Final > > > We should rename Deployment in tabbed properties to Replication Controller. I was complaining about it some times ago, but now I found also good reason to change it - underlying Kubernetes technology has Deployment resources and ReplicaSets (new generation of replication controller). And those resources are something a bit different although it has similar functionality. For users coming from Kubernetes world or those who are familiar with Kubernetes, could this be a bit misleading. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22959) Properties: rename Deployment to Replication Controller

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22959?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-22959. -------------------------------------- Resolution: Rejected > Properties: rename Deployment to Replication Controller > ------------------------------------------------------- > > Key: JBIDE-22959 > URL: https://issues.jboss.org/browse/JBIDE-22959 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: openshift_v3, properties > Fix For: 4.5.1.Final > > > We should rename Deployment in tabbed properties to Replication Controller. I was complaining about it some times ago, but now I found also good reason to change it - underlying Kubernetes technology has Deployment resources and ReplicaSets (new generation of replication controller). And those resources are something a bit different although it has similar functionality. For users coming from Kubernetes world or those who are familiar with Kubernetes, could this be a bit misleading. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22959) Properties: rename Deployment to Replication Controller

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22959?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-22959 at 10/28/17 5:28 PM: -------------------------------------------------------------------- 1y later the web-ui is still labelling Replication Controllers "Deployments" like we do. Resolving as REJECTED was (Author: adietish): 1y later the web-ui is still labelling Replication Controllers "Deployments" like we do. Resolving as WONT_FIX > Properties: rename Deployment to Replication Controller > ------------------------------------------------------- > > Key: JBIDE-22959 > URL: https://issues.jboss.org/browse/JBIDE-22959 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: openshift_v3, properties > Fix For: 4.5.1.Final > > > We should rename Deployment in tabbed properties to Replication Controller. I was complaining about it some times ago, but now I found also good reason to change it - underlying Kubernetes technology has Deployment resources and ReplicaSets (new generation of replication controller). And those resources are something a bit different although it has similar functionality. For users coming from Kubernetes world or those who are familiar with Kubernetes, could this be a bit misleading. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22959) Properties: rename Deployment to Replication Controller

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22959?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-22959: ---------------------------------------- Assignee: Andre Dietisheim > Properties: rename Deployment to Replication Controller > ------------------------------------------------------- > > Key: JBIDE-22959 > URL: https://issues.jboss.org/browse/JBIDE-22959 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: openshift_v3, properties > Fix For: 4.5.x > > > We should rename Deployment in tabbed properties to Replication Controller. I was complaining about it some times ago, but now I found also good reason to change it - underlying Kubernetes technology has Deployment resources and ReplicaSets (new generation of replication controller). And those resources are something a bit different although it has similar functionality. For users coming from Kubernetes world or those who are familiar with Kubernetes, could this be a bit misleading. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22860) Application Wizard: Improve layout for templates

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22860?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-22860. -------------------------------------- Assignee: Andre Dietisheim Resolution: Done > Application Wizard: Improve layout for templates > ------------------------------------------------ > > Key: JBIDE-22860 > URL: https://issues.jboss.org/browse/JBIDE-22860 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: application_wizard, openshift_v3 > Fix For: 4.4.4.Final > > > In the New OpenShift Application wizard we have 2 tabs for a decision on what should a new application be based. One for server-template-based application (either from templates or builder images) and one for "Local template". Problem with local template is that it supports usage of URL templates - I can provide an URL of a template. This is not really local template. I think we should rename "Local template" tab to "Custom template" or something what would suggest usage of URLs as well as templates from local file system. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22860) Application Wizard: Improve layout for templates

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22860?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22860: ------------------------------------- Fix Version/s: 4.4.4.Final (was: 4.5.x) > Application Wizard: Improve layout for templates > ------------------------------------------------ > > Key: JBIDE-22860 > URL: https://issues.jboss.org/browse/JBIDE-22860 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Priority: Minor > Labels: application_wizard, openshift_v3 > Fix For: 4.4.4.Final > > > In the New OpenShift Application wizard we have 2 tabs for a decision on what should a new application be based. One for server-template-based application (either from templates or builder images) and one for "Local template". Problem with local template is that it supports usage of URL templates - I can provide an URL of a template. This is not really local template. I think we should rename "Local template" tab to "Custom template" or something what would suggest usage of URLs as well as templates from local file system. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22860) Application Wizard: Improve layout for templates

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22860?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22860: ------------------------------------------ This was resolved with the PR for JBIDE-23473 > Application Wizard: Improve layout for templates > ------------------------------------------------ > > Key: JBIDE-22860 > URL: https://issues.jboss.org/browse/JBIDE-22860 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Priority: Minor > Labels: application_wizard, openshift_v3 > Fix For: 4.4.4.Final > > > In the New OpenShift Application wizard we have 2 tabs for a decision on what should a new application be based. One for server-template-based application (either from templates or builder images) and one for "Local template". Problem with local template is that it supports usage of URL templates - I can provide an URL of a template. This is not really local template. I think we should rename "Local template" tab to "Custom template" or something what would suggest usage of URLs as well as templates from local file system. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22691) Allow extensions to be injected with Eclipse services

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22691?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22691: ------------------------------------- Fix Version/s: 4.5.1.Final (was: 4.5.x) > Allow extensions to be injected with Eclipse services > ----------------------------------------------------- > > Key: JBIDE-22691 > URL: https://issues.jboss.org/browse/JBIDE-22691 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: common > Affects Versions: 4.4.1.AM1 > Reporter: John Steele > Assignee: John Steele > Fix For: 4.5.1.Final > > > We need a way to share services with extensions. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2017