February 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-21616) Main tab for CDK launch configuration is not whole by default

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21616?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21616: ------------------------------------- Theoretically you could provide a small example plugin with a launch config and a launch config tab group... and the group just showing these two tabs. That would not be a bug in the example plugin, but would demonstrate a bug in the upstream. I'll see if I can whip something up real quick. > Main tab for CDK launch configuration is not whole by default > ------------------------------------------------------------- > > Key: JBIDE-21616 > URL: https://issues.jboss.org/browse/JBIDE-21616 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Environment: Fedora 22, GTK3 > Reporter: Marián Labuda > Attachments: after.png, before.png > > > In launch configuration of a CDK server adapter there are 2 tabs - Main and Environment. Upon opening of launch configuration for a CDK server adapter, Main tab is preselected but there are only Location widgets available. > !before.png! > After switching to Environment tab and back, Working directory and Arguments widgets become available. > !after.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21616) Main tab for CDK launch configuration is not whole by default

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21616?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-21616: --------------------------------------- I am aware that it is not JBT specific at all but to report a bugzilla I should have some example where it is to be found (steps to reproduce). To let it be easily reproducible so they could fix it and verify it. > Main tab for CDK launch configuration is not whole by default > ------------------------------------------------------------- > > Key: JBIDE-21616 > URL: https://issues.jboss.org/browse/JBIDE-21616 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Environment: Fedora 22, GTK3 > Reporter: Marián Labuda > Attachments: after.png, before.png > > > In launch configuration of a CDK server adapter there are 2 tabs - Main and Environment. Upon opening of launch configuration for a CDK server adapter, Main tab is preselected but there are only Location widgets available. > !before.png! > After switching to Environment tab and back, Working directory and Arguments widgets become available. > !after.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21623) Tests: add tests for NewApplication wizard

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21623?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21623: -------------------------------- Issue Type: Task (was: Feature Request) > Tests: add tests for NewApplication wizard > ------------------------------------------ > > Key: JBIDE-21623 > URL: https://issues.jboss.org/browse/JBIDE-21623 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, tests > Fix For: 4.3.1.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21628) Server Adapter: Service widget is empty

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21628?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21628: ---------------------------------- Labels: openshift_v3 server_adapter (was: ) > Server Adapter: Service widget is empty > --------------------------------------- > > Key: JBIDE-21628 > URL: https://issues.jboss.org/browse/JBIDE-21628 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: openshift_v3, server_adapter > Attachments: empty_service.png > > > In OpenShift 3 Server Adapter overview are widgets with information related to server adapter. There is a text widget for a service but it is empty although server adapter is connected to a specific service. See following screenshot > !empty_service.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21628) Server Adapter: Service widget is empty

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21628: ------------------------------------- Summary: Server Adapter: Service widget is empty Key: JBIDE-21628 URL: https://issues.jboss.org/browse/JBIDE-21628 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.CR1 Reporter: Marián Labuda Attachments: empty_service.png In OpenShift 3 Server Adapter overview are widgets with information related to server adapter. There is a text widget for a service but it is empty although server adapter is connected to a specific service. See following screenshot !empty_service.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21627) Enable exposure of OpenShift resources in tooling

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21627?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21627: ------------------------------------- Do you have more details on that feature? > Enable exposure of OpenShift resources in tooling > ------------------------------------------------- > > Key: JBIDE-21627 > URL: https://issues.jboss.org/browse/JBIDE-21627 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: openshift_v3 > Fix For: 4.4.x > > > It would be nice if we would have something similar as oc binary to expose an existing resource. To expose existing pods or services. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21627) Enable exposure of OpenShift resources in tooling

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21627?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21627: -------------------------------- Fix Version/s: 4.4.x > Enable exposure of OpenShift resources in tooling > ------------------------------------------------- > > Key: JBIDE-21627 > URL: https://issues.jboss.org/browse/JBIDE-21627 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: openshift_v3 > Fix For: 4.4.x > > > It would be nice if we would have something similar as oc binary to expose an existing resource. To expose existing pods or services. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21626) Pod is not created when docker image is deployed to OpenShift

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21626?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21626: ----------------------------------- Assignee: Jeff Cantrill > Pod is not created when docker image is deployed to OpenShift > ------------------------------------------------------------- > > Key: JBIDE-21626 > URL: https://issues.jboss.org/browse/JBIDE-21626 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Priority: Critical > Labels: openshift_v3 > Fix For: 4.3.1.CR1 > > > When deploying a docker image to OpenShift via oc binary, pod where the image is supposed to run is created, together with service and router. But when deploying a docker image to OpenShift via OpenShift tools, no pod is created, only service and router. When using cli, pod is created later (what I noticed, there is different pull policy between creating from cli with "oc new-app docker-image" and creating from IDE). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21627) Enable exposure of OpenShift resources in tooling

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21627: ------------------------------------- Summary: Enable exposure of OpenShift resources in tooling Key: JBIDE-21627 URL: https://issues.jboss.org/browse/JBIDE-21627 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.3.1.CR1 Reporter: Marián Labuda It would be nice if we would have something similar as oc binary to expose an existing resource. To expose existing pods or services. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21626) Pod is not created when docker image is deployed to OpenShift

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21626?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21626: -------------------------------- Fix Version/s: 4.3.1.CR1 > Pod is not created when docker image is deployed to OpenShift > ------------------------------------------------------------- > > Key: JBIDE-21626 > URL: https://issues.jboss.org/browse/JBIDE-21626 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Priority: Critical > Labels: openshift_v3 > Fix For: 4.3.1.CR1 > > > When deploying a docker image to OpenShift via oc binary, pod where the image is supposed to run is created, together with service and router. But when deploying a docker image to OpenShift via OpenShift tools, no pod is created, only service and router. When using cli, pod is created later (what I noticed, there is different pull policy between creating from cli with "oc new-app docker-image" and creating from IDE). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 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 February 2016