March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21920) Cannot use features which are using oc binary

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21920?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21920: ------------------------------------------ [~mlabuda] can you please provide more precise steps to reproduce this? I tried to reproduce this but couldnt. Futhermore I'm also using the server adapter with oc on a daily base and this never happened to me so far. > Cannot use features which are using oc binary > --------------------------------------------- > > Key: JBIDE-21920 > URL: https://issues.jboss.org/browse/JBIDE-21920 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Priority: Blocker > Labels: openshift_v3 > Fix For: 4.3.1.CR1 > > > After latest update of nightly JBT I am not able to get logs from pods(/builds) or work with server adapter, because there is something wrong with setting oc path. When I set path on OpenShift 3 preference page to be pointing to correct oc binary, following e.g. getting log from pod results in showing following message in console > {code} > The OpenShift 'oc' binary location was not specified. Set the property openshift.restclient.oc.location > {code} > There is no stack trace available for this error in error log. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21920) Cannot use features which are using oc binary

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21920?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21920: ------------------------------------- Fix Version/s: 4.3.1.CR1 > Cannot use features which are using oc binary > --------------------------------------------- > > Key: JBIDE-21920 > URL: https://issues.jboss.org/browse/JBIDE-21920 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Priority: Blocker > Labels: openshift_v3 > Fix For: 4.3.1.CR1 > > > After latest update of nightly JBT I am not able to get logs from pods(/builds) or work with server adapter, because there is something wrong with setting oc path. When I set path on OpenShift 3 preference page to be pointing to correct oc binary, following e.g. getting log from pod results in showing following message in console > {code} > The OpenShift 'oc' binary location was not specified. Set the property openshift.restclient.oc.location > {code} > There is no stack trace available for this error in error log. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3653) User's home folder with spaces cannot be used by vagrant during install

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3653?page=com.atlassian.jira.plugin.... ] Jan Richter edited comment on JBDS-3653 at 3/21/16 7:46 AM: ------------------------------------------------------------ Exactly what with is my help needed? Just point me in the right direction :) Regarding the NAME~1 shortcut, first it will still be interpreted as the full path in the end, second if by some accident there are more folders with the same prefix, you can't know for sure which one has the right index in this short notation (unless you look at the contents that is). was (Author: jrichter1): Exactly what with is my help needed? Just point me in the right direction :) Regarding the NAME~1 shortcut, first it will still be interpreted as the full path in the end, second if by some accident there are more folders with the same prefix, you can't know for sure which one has the right index in this short notation. > User's home folder with spaces cannot be used by vagrant during install > ----------------------------------------------------------------------- > > Key: JBDS-3653 > URL: https://issues.jboss.org/browse/JBDS-3653 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > Attachments: install(1).log > > > Vagrant complains about > {quote}Wed, 02 Mar 2016 18:04:21 GMT-ERROR: cdk - Error: Command failed: C:\WINDOWS\system32\cmd.exe /s /c "vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.0.0.gem" > The directory where plugins are installed (the Vagrant home directory) > has a space in it. On Windows, there is a bug in Ruby when compiling > plugins into directories with spaces. Please move your Vagrant home > directory to a path without spaces and try again > {quote} > When user home directory have spaces in it, because .vagrant.d file path in turn has spaces as well. For instance: > {code}C:\Users\User Name\.vagrant.d{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3653) User's home folder with spaces cannot be used by vagrant during install

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3653?page=com.atlassian.jira.plugin.... ] Jan Richter commented on JBDS-3653: ----------------------------------- Exactly what with is my help needed? Just point me in the right direction :) Regarding the NAME~1 shortcut, first it will still be interpreted as the full path in the end, second if by some accident there are more folders with the same prefix, you can't know for sure which one has the right index in this short notation. > User's home folder with spaces cannot be used by vagrant during install > ----------------------------------------------------------------------- > > Key: JBDS-3653 > URL: https://issues.jboss.org/browse/JBDS-3653 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > Attachments: install(1).log > > > Vagrant complains about > {quote}Wed, 02 Mar 2016 18:04:21 GMT-ERROR: cdk - Error: Command failed: C:\WINDOWS\system32\cmd.exe /s /c "vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.0.0.gem" > The directory where plugins are installed (the Vagrant home directory) > has a space in it. On Windows, there is a bug in Ruby when compiling > plugins into directories with spaces. Please move your Vagrant home > directory to a path without spaces and try again > {quote} > When user home directory have spaces in it, because .vagrant.d file path in turn has spaces as well. For instance: > {code}C:\Users\User Name\.vagrant.d{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21921) Created OS 3 Server Adapter is stopped

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21921?page=com.atlassian.jira.plugi... ] Marián Labuda resolved JBIDE-21921. ----------------------------------- Resolution: Done > Created OS 3 Server Adapter is stopped > -------------------------------------- > > Key: JBIDE-21921 > URL: https://issues.jboss.org/browse/JBIDE-21921 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > > When I create a new OpenShift 3 server adapter it is stopped by default. It requires me to start it. Newly created OS 3 server adapters should be started by default. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21921) Created OS 3 Server Adapter is stopped

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21921: ------------------------------------- Summary: Created OS 3 Server Adapter is stopped Key: JBIDE-21921 URL: https://issues.jboss.org/browse/JBIDE-21921 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.CR1 Reporter: Marián Labuda Assignee: Rob Stryker Fix For: 4.3.1.CR1 When I create a new OpenShift 3 server adapter it is stopped by default. It requires me to start it. Newly created OS 3 server adapters should be started by default. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21901) Created OS 3 Server Adapter is stopped

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21901?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21901. --------------------------------- Verified on nightly build of JBT with OpenShift plugin build B240. > Created OS 3 Server Adapter is stopped > -------------------------------------- > > Key: JBIDE-21901 > URL: https://issues.jboss.org/browse/JBIDE-21901 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Rob Stryker > Fix For: 4.3.1.CR1 > > > When I create a new OpenShift 3 server adapter it is stopped by default. It requires me to start it. Newly created OS 3 server adapters should be started by default. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21921) Created OS 3 Server Adapter is stopped

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21921?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21921: ---------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.CR1) > Created OS 3 Server Adapter is stopped > -------------------------------------- > > Key: JBIDE-21921 > URL: https://issues.jboss.org/browse/JBIDE-21921 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > > When I create a new OpenShift 3 server adapter it is stopped by default. It requires me to start it. Newly created OS 3 server adapters should be started by default. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21920) Cannot use features which are using oc binary

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21920: ------------------------------------- Summary: Cannot use features which are using oc binary Key: JBIDE-21920 URL: https://issues.jboss.org/browse/JBIDE-21920 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.CR1 Reporter: Marián Labuda Priority: Blocker After latest update of nightly JBT I am not able to get logs from pods(/builds) or work with server adapter, because there is something wrong with setting oc path. When I set path on OpenShift 3 preference page to be pointing to correct oc binary, following e.g. getting log from pod results in showing following message in console {code} The OpenShift 'oc' binary location was not specified. Set the property openshift.restclient.oc.location {code} There is no stack trace available for this error in error log. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21920) Cannot use features which are using oc binary

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21920?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21920: ---------------------------------- Labels: openshift_v3 (was: ) > Cannot use features which are using oc binary > --------------------------------------------- > > Key: JBIDE-21920 > URL: https://issues.jboss.org/browse/JBIDE-21920 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Priority: Blocker > Labels: openshift_v3 > > After latest update of nightly JBT I am not able to get logs from pods(/builds) or work with server adapter, because there is something wrong with setting oc path. When I set path on OpenShift 3 preference page to be pointing to correct oc binary, following e.g. getting log from pod results in showing following message in console > {code} > The OpenShift 'oc' binary location was not specified. Set the property openshift.restclient.oc.location > {code} > There is no stack trace available for this error in error log. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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