March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21843) CDK Poller always fails on OSX

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21843?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21843: -------------------------------- Issue Type: Bug (was: Feature Request) > CDK Poller always fails on OSX > ------------------------------ > > Key: JBIDE-21843 > URL: https://issues.jboss.org/browse/JBIDE-21843 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Environment: OSX > Reporter: Fred Bricon > Assignee: Rob Stryker > Priority: Critical > > Starting the CDK on OSX always fails. Whether it was already started from CLI or not. > The vagrant up command is properly executed, you can see the output in the console, but it ends up with a message "Server CDK Server Adapter at localhost failed to start." > {noformat} > VagrantPoller.parseOutput(String[]) line: 220 > VagrantPoller.onePing(IServer, String) line: 160 > VagrantPoller.onePing(IServer) line: 138 > VagrantPoller.getCurrentStateSynchronous(IServer) line: 114 > CDKLaunchController$2.run() line: 222 > {noformat} > In parseOutput, the value of lines is : > [1457536005,,error-exit,Vagrant::Errors::ProviderNotUsable,The provider 'virtualbox' that was requested to back the machine\n'cdk' is reporting that it isn't usable on this system. The\nreason is shown below:\n\nVagrant could not detect VirtualBox! Make sure VirtualBox is properly installed.\nVagrant uses the `VBoxManage` binary that ships with VirtualBox%!(VAGRANT_COMMA) and requires\nthis to be available on the PATH. If VirtualBox is installed%!(VAGRANT_COMMA) please find the\n`VBoxManage` binary and add it to the PATH environmental variable.] > this is not properly parsed as it later goes into this block > {code} > Collection<VagrantStatus> stats = status.values(); > if( stats.size() == 0 ) { > return IStatus.ERROR; > } > {code} > And the message in the lines is lost completely -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21840) Checkbox to save password in Secure Storage is not checked when password is stored

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21840?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21840: ------------------------------------- Fix Version/s: 4.3.1.CR1 > Checkbox to save password in Secure Storage is not checked when password is stored > ---------------------------------------------------------------------------------- > > Key: JBIDE-21840 > URL: https://issues.jboss.org/browse/JBIDE-21840 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: connection_wizard, openshift_v3 > Fix For: 4.3.1.CR1 > > > In OpenShift connection wizard there is a checkbox to store password/token in secure storage. If I choose on an existing OpenShift 3 connection with basic authentication to store password in secure storage, technically it is stored and visible on Secure Storage preference page, but in Connection wizard it is not visible. Upon next opening of the Edit Connection wizard, checkbox is unchecked although password is checked. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21840) Checkbox to save password in Secure Storage is not checked when password is stored

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21840?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-21840: ---------------------------------------- Assignee: Andre Dietisheim > Checkbox to save password in Secure Storage is not checked when password is stored > ---------------------------------------------------------------------------------- > > Key: JBIDE-21840 > URL: https://issues.jboss.org/browse/JBIDE-21840 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: connection_wizard, openshift_v3 > Fix For: 4.3.1.CR1 > > > In OpenShift connection wizard there is a checkbox to store password/token in secure storage. If I choose on an existing OpenShift 3 connection with basic authentication to store password in secure storage, technically it is stored and visible on Secure Storage preference page, but in Connection wizard it is not visible. Upon next opening of the Edit Connection wizard, checkbox is unchecked although password is checked. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21840) Checkbox to save password in Secure Storage is not checked when password is stored

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21840?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-21840: ---------------------------------------- Assignee: (was: Andre Dietisheim) > Checkbox to save password in Secure Storage is not checked when password is stored > ---------------------------------------------------------------------------------- > > Key: JBIDE-21840 > URL: https://issues.jboss.org/browse/JBIDE-21840 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: connection_wizard, openshift_v3 > Fix For: 4.3.1.CR1 > > > In OpenShift connection wizard there is a checkbox to store password/token in secure storage. If I choose on an existing OpenShift 3 connection with basic authentication to store password in secure storage, technically it is stored and visible on Secure Storage preference page, but in Connection wizard it is not visible. Upon next opening of the Edit Connection wizard, checkbox is unchecked although password is checked. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21307) Server Adapter: ensure oc binary that's used for rsync is v1.1.1+

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21307?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21307: ------------------------------------------ [~maxandersen] in the particular case you ran into it's a bug in the oc binary, no error is spit out, you would simply have no idea why it fails unless you are aware that your version is outdated and buggy. > Server Adapter: ensure oc binary that's used for rsync is v1.1.1+ > ----------------------------------------------------------------- > > Key: JBIDE-21307 > URL: https://issues.jboss.org/browse/JBIDE-21307 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Labels: oc_binary, openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > > Because of https://github.com/openshift/origin/issues/6109 publishing with the server adapter (which does a oc rsync behind the scenes) only properly works with oc v1.1.1. Versions below require the user to manually > {code} > oc login --server=<server that we publish to> --token=... > {code} > We should check the version and warn if the user is using an oc that is older than this. > the changelog of oc in [v1.1.1|https://github.com/openshift/origin/releases/tag/v1.1.1] states the following refering to the issue: > {quote} > Support some of the global rsync flags on oc rsync for displaying progress information - not supported on all rsync backends (like tar) > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21837) OpenShift server adpter editor: link 'Open launch configuration' throws exception

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21837?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21837: ------------------------------------------ [~scabanovich] ah, gotcha, missed that actually. Thanks for pointing out. > OpenShift server adpter editor: link 'Open launch configuration' throws exception > --------------------------------------------------------------------------------- > > Key: JBIDE-21837 > URL: https://issues.jboss.org/browse/JBIDE-21837 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Labels: openshift_v2, openshift_v3, server_adapter_editor > Fix For: 4.4.0.Alpha1 > > Attachments: ErrorAtEditLaunchConfig.png > > > There is no launch configuration tab groups bound to the openshift launch type. > As the result, an exception is caught at opening 'Edit Configuration' wizard. The exception is not logged, but user has to click OK on two successive Error and Problem occurred message dialogs and finally gets the wizard with empty Name input and error message 'A name is required for the configuration'. > This user unfriendly behaviour may be considered an upstream issue, but the workaround is just to bind an empty list of tab groups. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21837) OpenShift server adpter editor: link 'Open launch configuration' throws exception

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21837?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21837: ------------------------------------- Labels: openshift_v2 openshift_v3 server_adapter_editor (was: openshift_v2 server_adapter_editor) > OpenShift server adpter editor: link 'Open launch configuration' throws exception > --------------------------------------------------------------------------------- > > Key: JBIDE-21837 > URL: https://issues.jboss.org/browse/JBIDE-21837 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Labels: openshift_v2, openshift_v3, server_adapter_editor > Fix For: 4.4.0.Alpha1 > > Attachments: ErrorAtEditLaunchConfig.png > > > There is no launch configuration tab groups bound to the openshift launch type. > As the result, an exception is caught at opening 'Edit Configuration' wizard. The exception is not logged, but user has to click OK on two successive Error and Problem occurred message dialogs and finally gets the wizard with empty Name input and error message 'A name is required for the configuration'. > This user unfriendly behaviour may be considered an upstream issue, but the workaround is just to bind an empty list of tab groups. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21841) Shortened repo URL in Import wizard is weird

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21841?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21841: ------------------------------------------ [~mlabuda] Me as a dev I'd want to know of the actual server of the repo, it matters to me, just having the repo-name is imho not enough. [~fbricon] WDYT? > Shortened repo URL in Import wizard is weird > -------------------------------------------- > > Key: JBIDE-21841 > URL: https://issues.jboss.org/browse/JBIDE-21841 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: import_wizard, openshift_v3 > Attachments: shortened_repo_url.png > > > When Importing an OpenShift 3 application via File - Import - Existing OpenShift Application, there is a wizard page to select a build config to import application repo. We should display repo name as styled text with style (grayed) and it should not be shorten or at least not like this when there is missing a part in the middle of URL. > !shortened_repo_url.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21841) Shortened repo URL in Import wizard is weird

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21841?page=com.atlassian.jira.plugi... ] Marián Labuda edited comment on JBIDE-21841 at 3/9/16 9:57 AM: --------------------------------------------------------------- What if there would be just user/repository or just repository \[branch] and tooltip would show whole URL? Or something similar. It would be similar what would user see in Project explorer then. I think it would not be usual to have repository with same name under one project. There would have been several build configs with different name etc... because of resource name conflicts. It could look like this: eap-app {color:#cccccc} jboss-eap-quickstarts \[6.4.x] {color} There would be marker to let user know there is a tooltip and tooltip would show full URL. Is it really necessary to have whole URL listed there when we have a build config available under a specific project? was (Author: mlabuda): What if there would be just user/repository or just repository \[branch] and tooltip would show whole URL? Or something similar. It would be similar what would user see in Project explorer then: eap-app {color:#cccccc} jboss-eap-quickstarts \[6.4.x] {color} Is it really necessary to have whole URL listed there when we have a build config available under a specific project? > Shortened repo URL in Import wizard is weird > -------------------------------------------- > > Key: JBIDE-21841 > URL: https://issues.jboss.org/browse/JBIDE-21841 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: import_wizard, openshift_v3 > Attachments: shortened_repo_url.png > > > When Importing an OpenShift 3 application via File - Import - Existing OpenShift Application, there is a wizard page to select a build config to import application repo. We should display repo name as styled text with style (grayed) and it should not be shorten or at least not like this when there is missing a part in the middle of URL. > !shortened_repo_url.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21841) Shortened repo URL in Import wizard is weird

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21841?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-21841: --------------------------------------- What if there would be just user/repository or just repository \[branch] and tooltip would show whole URL? Or something similar. It would be similar what would user see in Project explorer then: eap-app {color:#cccccc} jboss-eap-quickstarts \[6.4.x] {color} Is it really necessary to have whole URL listed there when we have a build config available under a specific project? > Shortened repo URL in Import wizard is weird > -------------------------------------------- > > Key: JBIDE-21841 > URL: https://issues.jboss.org/browse/JBIDE-21841 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: import_wizard, openshift_v3 > Attachments: shortened_repo_url.png > > > When Importing an OpenShift 3 application via File - Import - Existing OpenShift Application, there is a wizard page to select a build config to import application repo. We should display repo name as styled text with style (grayed) and it should not be shorten or at least not like this when there is missing a part in the middle of URL. > !shortened_repo_url.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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