July 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26145) Add minishift Start/Stop support

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26145?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-26145: -------------------------------- Fix Version/s: 4.6.0.Final > Add minishift Start/Stop support > -------------------------------- > > Key: JBIDE-26145 > URL: https://issues.jboss.org/browse/JBIDE-26145 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: stack-server-protocol > Reporter: Denis Golovin > Assignee: Rob Stryker > Fix For: 4.6.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26145) Add minishift Start/Stop support

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26145?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-26145. --------------------------------- Resolution: Done * | 4e0f653 - Minishift support - initial implementation (12 days ago) <Rob Stryker> > Add minishift Start/Stop support > -------------------------------- > > Key: JBIDE-26145 > URL: https://issues.jboss.org/browse/JBIDE-26145 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: stack-server-protocol > Reporter: Denis Golovin > Assignee: Rob Stryker > Fix For: 4.6.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26199) No response when adding a discovery path for the 2nd time / removing a non existing path

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26199?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-26199: -------------------------------- Fix Version/s: 4.6.0.Final > No response when adding a discovery path for the 2nd time / removing a non existing path > ---------------------------------------------------------------------------------------- > > Key: JBIDE-26199 > URL: https://issues.jboss.org/browse/JBIDE-26199 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: stack-server-protocol > Affects Versions: 4.6.0.Final > Reporter: Jan Richter > Assignee: Rob Stryker > Fix For: 4.6.0.Final > > > server/addDiscoveryPath should have some way of notifying the client when it's trying to add a discovery path that has already been added. > same goes for server/removeDiscoveryPath when the path doesn't exist on the server -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26199) No response when adding a discovery path for the 2nd time / removing a non existing path

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26199?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-26199. --------------------------------- Resolution: Done pushed fix to master > No response when adding a discovery path for the 2nd time / removing a non existing path > ---------------------------------------------------------------------------------------- > > Key: JBIDE-26199 > URL: https://issues.jboss.org/browse/JBIDE-26199 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: stack-server-protocol > Affects Versions: 4.6.0.Final > Reporter: Jan Richter > Assignee: Rob Stryker > Fix For: 4.6.0.Final > > > server/addDiscoveryPath should have some way of notifying the client when it's trying to add a discovery path that has already been added. > same goes for server/removeDiscoveryPath when the path doesn't exist on the server -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26098) Update dependencies in org.jboss.tools.stacks and repair test failures in jbosstools_base-master job

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26098?page=com.atlassian.jira.plugi... ] Ondrej Dockal commented on JBIDE-26098: --------------------------------------- [~nickboldt] Do you think that upversioning of dependent components mentioned in point 2 would break anything? > Update dependencies in org.jboss.tools.stacks and repair test failures in jbosstools_base-master job > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-26098 > URL: https://issues.jboss.org/browse/JBIDE-26098 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: qa > Affects Versions: 4.6.0.Final > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Fix For: 4.9.0.AM1 > > > 1. Have stacks tests to be run on jenkins jbt-base master and pull request job and have them green (not just omitting stacks tests results). > 2. Update versions of maven plugins used as libraries in org.jboss.tools.stacks plugin: > * org.jboss.jdf.stacks-client; 1.0.3.Final -> no change > * org.yaml.snakeyaml; 1.10 -> 1.18 > * org.apache.httpcomponents.httpclient; 4.0.1 -> 4.5.5 > * org.apache.httpcomponents.httpcore; 4.0.1 -> 4.4.9 > * org.jboss.logging.jboss-logging; 3.1.2.GA -> 3.3.2.Final > 3. Run all stacks.tests available (only one test class was run) > 4. Check on dependencies and usages in org.jboss.jdf.stacks-client and org.jboss.tools.stacks (what needs to be update, does it broke something, what else is using it) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26098) Update dependencies in org.jboss.tools.stacks and repair test failures in jbosstools_base-master job

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26098?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-26098: ---------------------------------- Summary: Update dependencies in org.jboss.tools.stacks and repair test failures in jbosstools_base-master job (was: Repair org.jboss.tools.stacks test failures in jbosstools_base-master job) > Update dependencies in org.jboss.tools.stacks and repair test failures in jbosstools_base-master job > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-26098 > URL: https://issues.jboss.org/browse/JBIDE-26098 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: qa > Affects Versions: 4.6.0.Final > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Fix For: 4.9.0.AM1 > > > 1. Have stacks tests to be run on jenkins jbt-base master and pull request job and have them green (not just omitting stacks tests results). > 2. Update versions of maven plugins used as libraries in org.jboss.tools.stacks plugin: > * org.jboss.jdf.stacks-client; 1.0.3.Final -> no change > * org.yaml.snakeyaml; 1.10 -> 1.18 > * org.apache.httpcomponents.httpclient; 4.0.1 -> 4.5.5 > * org.apache.httpcomponents.httpcore; 4.0.1 -> 4.4.9 > * org.jboss.logging.jboss-logging; 3.1.2.GA -> 3.3.2.Final > 3. Run all stacks.tests available (only one test class was run) > 4. Check on dependencies and usages in org.jboss.jdf.stacks-client and org.jboss.tools.stacks (what needs to be update, does it broke something, what else is using it) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26204) Pod Log: console shows up empty when you use a bogus oc executable

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26204?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-26204: ------------------------------------- Description: steps: # ASSERT: use the code that in the [PR|https://github.com/jbosstools/jbosstools-openshift/pull/1772] for JBIDE-25700 # ASSERT: make sure you have an app with a pod running in OpenShift # EXEC: open OpenShift preferences and point it to an oc that is a bogus executable file (that you created ex. by doing "touch oc && chmod +x oc") # EXEC: in OpenShift Explorer: select the pod and pick "Pod Log..." Result: The "Console" view shows up but nothing happens, there's no output. was: steps: # ASSERT: use the code that in the [PR|https://github.com/jbosstools/jbosstools-openshift/pull/1772] for JBIDE-25700 # ASSERT: make sure you have an app with a pod running in OpenShift # EXEC: open OpenShift preferences and point it to an oc in a folder that contains spaces (ex. "~/oc binaries/3.41/oc") # EXEC: in OpenShift Explorer: select the pod and pick "Pod Log..." Result: The "Console" view shows up but nothing happens, there's no output. > Pod Log: console shows up empty when you use a bogus oc executable > ------------------------------------------------------------------ > > Key: JBIDE-26204 > URL: https://issues.jboss.org/browse/JBIDE-26204 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.9.0.AM1 > > > steps: > # ASSERT: use the code that in the [PR|https://github.com/jbosstools/jbosstools-openshift/pull/1772] for JBIDE-25700 > # ASSERT: make sure you have an app with a pod running in OpenShift > # EXEC: open OpenShift preferences and point it to an oc that is a bogus executable file (that you created ex. by doing "touch oc && chmod +x oc") > # EXEC: in OpenShift Explorer: select the pod and pick "Pod Log..." > Result: > The "Console" view shows up but nothing happens, there's no output. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26204) Pod Log: console shows up empty when you use a bogus oc executable

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26204?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-26204: ------------------------------------- Summary: Pod Log: console shows up empty when you use a bogus oc executable (was: Pod Log: empty console shows up when you use an oc whose path contains " ") > Pod Log: console shows up empty when you use a bogus oc executable > ------------------------------------------------------------------ > > Key: JBIDE-26204 > URL: https://issues.jboss.org/browse/JBIDE-26204 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.9.0.AM1 > > > steps: > # ASSERT: use the code that in the [PR|https://github.com/jbosstools/jbosstools-openshift/pull/1772] for JBIDE-25700 > # ASSERT: make sure you have an app with a pod running in OpenShift > # EXEC: open OpenShift preferences and point it to an oc in a folder that contains spaces (ex. "~/oc binaries/3.41/oc") > # EXEC: in OpenShift Explorer: select the pod and pick "Pod Log..." > Result: > The "Console" view shows up but nothing happens, there's no output. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26221) Server adapter wizard: reconfiguring oc will cause warning, where it should error

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26221?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-26221: ------------------------------------------ In JBIDE-26173 we decided to have all problems in oc warnings only. In the server adapter wizard, problems with the oc binary on the other hand need to be errors. This issue is a usecase where turning warnings into errors for the server adapter wizard was missed. > Server adapter wizard: reconfiguring oc will cause warning, where it should error > --------------------------------------------------------------------------------- > > Key: JBIDE-26221 > URL: https://issues.jboss.org/browse/JBIDE-26221 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.9.0.AM1 > Reporter: Andre Dietisheim > Fix For: 4.9.0.AM1 > > Attachments: image-2018-07-18-17-15-31-065.png, image-2018-07-18-17-21-42-843.png > > > # ASSERT: have a project with a service running on OpenShift > # ASSERT: have the [PR|https://github.com/jbosstools/jbosstools-openshift/pull/1772] applied to your code > # ASSERT: in OpenShift Preferences: have oc not configured (or alternatively have it pointed to a location with a " " - ex. ~/oc binaries/oc) -> in both cases preferences will display a warning > # EXEC: launch server adapter wizard for your service > # ASSERT: server adapter wizard shows an error with a link to "configure" the oc binary > !image-2018-07-18-17-15-31-065.png! > # EXEC: hit "configure" and then in preferences configure a fake oc file (ex. a dummy file that you created with "touch ~/oc && chmod +x oc"). > # ASSERT: after closing preferences you're back in the server adapter wizard > Result: > Server adapter wizard now shows a warning, while it should show an error > !image-2018-07-18-17-21-42-843.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26221) Server adapter wizard: reconfiguring oc will cause warning, where it should error

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26221?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-26221: ------------------------------------------ This issue will be included in the fix for JBIDE-25700 > Server adapter wizard: reconfiguring oc will cause warning, where it should error > --------------------------------------------------------------------------------- > > Key: JBIDE-26221 > URL: https://issues.jboss.org/browse/JBIDE-26221 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.9.0.AM1 > Reporter: Andre Dietisheim > Fix For: 4.9.0.AM1 > > Attachments: image-2018-07-18-17-15-31-065.png, image-2018-07-18-17-21-42-843.png > > > # ASSERT: have a project with a service running on OpenShift > # ASSERT: have the [PR|https://github.com/jbosstools/jbosstools-openshift/pull/1772] applied to your code > # ASSERT: in OpenShift Preferences: have oc not configured (or alternatively have it pointed to a location with a " " - ex. ~/oc binaries/oc) -> in both cases preferences will display a warning > # EXEC: launch server adapter wizard for your service > # ASSERT: server adapter wizard shows an error with a link to "configure" the oc binary > !image-2018-07-18-17-15-31-065.png! > # EXEC: hit "configure" and then in preferences configure a fake oc file (ex. a dummy file that you created with "touch ~/oc && chmod +x oc"). > # ASSERT: after closing preferences you're back in the server adapter wizard > Result: > Server adapter wizard now shows a warning, while it should show an error > !image-2018-07-18-17-21-42-843.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 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 July 2018