April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22275) oc version is not recognized

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22275?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-22275: ------------------------------------- can you paste the output of the `oc version` command? > oc version is not recognized > ---------------------------- > > Key: JBIDE-22275 > URL: https://issues.jboss.org/browse/JBIDE-22275 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: openshift_v3 > Attachments: oc_warning.png > > > Using latest oc binary (1.2.0.RC2) there is an invalid warning message in OpenShift 3 preference page. It says my version is 0.0.0 and I need at least 1.1:1, although binary is 1.2.0. > !oc_warning.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-684) Removed org.eclipse.swtbot dependency + more refactoring

by stanislav kaleta (JIRA)

[ https://issues.jboss.org/browse/JBTIS-684?page=com.atlassian.jira.plugin.... ] stanislav kaleta updated JBTIS-684: ----------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-integration-stack-tests/pull/705 > Removed org.eclipse.swtbot dependency + more refactoring > -------------------------------------------------------- > > Key: JBTIS-684 > URL: https://issues.jboss.org/browse/JBTIS-684 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: QE, teiid > Affects Versions: 4.2.5.Final, 4.3.0.Beta1 > Reporter: stanislav kaleta > Assignee: stanislav kaleta > Fix For: 4.3.0.Beta1, 4.2.6.CR2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21401) SSL certificate dialog: Provide a way to change one's mind about accepting an SSL certificate

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21401?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21401. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5255. > SSL certificate dialog: Provide a way to change one's mind about accepting an SSL certificate > --------------------------------------------------------------------------------------------- > > Key: JBIDE-21401 > URL: https://issues.jboss.org/browse/JBIDE-21401 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jan Richter > Assignee: Viacheslav Kabanovich > Labels: openshift_v2, openshift_v3 > Fix For: 4.4.0.Alpha1 > > > The tooling will only give the user one chance to accept/deny the SSL certificate, which happens on start of the session. This is particularly annoying when for some reason the user denies the certificate (or just cancels the dialog) because the only way to reset it is to restart the IDE. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21300) OC binary should be looked up on $PATH if the user doesnt provide a specific location

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21300?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21300. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5255. > OC binary should be looked up on $PATH if the user doesnt provide a specific location > ------------------------------------------------------------------------------------- > > Key: JBIDE-21300 > URL: https://issues.jboss.org/browse/JBIDE-21300 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Fred Bricon > Labels: openshift_v3 > Fix For: 4.4.0.Alpha1 > > > For port forwarding, log streming and rsyinc the tooling requires an oc binary to be installed on the local machine. The user is asked to to set the location of this binary in the OpenShift 3 preferences. He can do this either manually by browsing and pointing to the binary or by hitting "Restore Defaults" which looks it up in the $PATH. > We should lookup the binary in $PATH if the user doesnt provide anything, we should not error and tell the user to set the location as we do currently. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21288) Add Manage Projects link to Deploy Docker Image dialog

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21288?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21288. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5255. > Add Manage Projects link to Deploy Docker Image dialog > ------------------------------------------------------ > > Key: JBIDE-21288 > URL: https://issues.jboss.org/browse/JBIDE-21288 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Labels: docker > Fix For: 4.4.0.Alpha1 > > > If there is no project for a OpenShift 3 connection it is not possible to proceed through Deploy Docker Image dialog opened via context menu of a OpenShift 3 connection. Because combo box for an OpenShift Project is empty and there is no Manage Projects link, one similar to the one in New OpenShift Application wizard. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21403) CDK server in Starting state and cannot be stopped with wrong path to vagrant

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21403?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21403: ---------------------------------- Component/s: cdk (was: openshift) > CDK server in Starting state and cannot be stopped with wrong path to vagrant > ----------------------------------------------------------------------------- > > Key: JBIDE-21403 > URL: https://issues.jboss.org/browse/JBIDE-21403 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > > When I first set up a CDK 2 Beta3 server adapter in Eclipse, it had the launch config set up with the wrong path to vagrant - /usr/bin/vagrant instead of /usr/local/bin/vagrant which is the default location on OS X - I didn't notice this and just tried to start the adapter. > Obviously it failed, but I was left in a state where the server was Starting and I couldn't stop it unless I restarted the IDE. > I think it should fail more gracefully. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21345) Server Adapter: Can finish wizard after picking connection, should not be able to

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21345?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21345. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5255. > Server Adapter: Can finish wizard after picking connection, should not be able to > ---------------------------------------------------------------------------------- > > Key: JBIDE-21345 > URL: https://issues.jboss.org/browse/JBIDE-21345 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter_wizard > Fix For: 4.4.0.Alpha1 > > Attachments: finish-enabled.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22275) oc version is not recognized

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22275?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22275: ---------------------------------- Labels: openshift_v3 (was: ) > oc version is not recognized > ---------------------------- > > Key: JBIDE-22275 > URL: https://issues.jboss.org/browse/JBIDE-22275 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: openshift_v3 > Attachments: oc_warning.png > > > Using latest oc binary (1.2.0.RC2) there is an invalid warning message in OpenShift 3 preference page. It says my version is 0.0.0 and I need at least 1.1:1, although binary is 1.2.0. > !oc_warning.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22275) oc version is not recognized

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-22275: ------------------------------------- Summary: oc version is not recognized Key: JBIDE-22275 URL: https://issues.jboss.org/browse/JBIDE-22275 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.0.Alpha1 Reporter: Marián Labuda Attachments: oc_warning.png Using latest oc binary (1.2.0.RC2) there is an invalid warning message in OpenShift 3 preference page. It says my version is 0.0.0 and I need at least 1.1:1, although binary is 1.2.0. !oc_warning.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22274) Show In->System Explorer on docker volume is not working when the volume is just a file (not a directory)

by Radim Hopp (JIRA)

Radim Hopp created JBIDE-22274: ---------------------------------- Summary: Show In->System Explorer on docker volume is not working when the volume is just a file (not a directory) Key: JBIDE-22274 URL: https://issues.jboss.org/browse/JBIDE-22274 Project: Tools (JBoss Tools) Issue Type: Bug Components: docker Affects Versions: 4.4.0.Alpha1 Environment: JBDS 10.0.0.Alpha1-v20160428-0509-B5247 Reporter: Radim Hopp Start docker container with -v parameter pointing to some file. For example: "docker run -d -p 5000:5000 -v /home/rhopp/temp/config.yml_new:/etc/docker/registry/config.yml --name registry1 registry:2" Go to Docker Explorer, expand running container->right click on the only volume in there->Show In->System Explorer-> Error is logged: {noformat:title=Failed to open in Web Browser} java.io.IOException: Cannot run program "/bin/sh" (in directory "/home/rhopp/temp/config.yml_new"): error=20, Not a directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at java.lang.Runtime.exec(Runtime.java:620) at org.eclipse.linuxtools.internal.docker.ui.commands.ShowInSystemExplorerCommandHandler.getLaunchProcess(ShowInSystemExplorerCommandHandler.java:99) at org.eclipse.linuxtools.internal.docker.ui.commands.ShowInSystemExplorerCommandHandler.access$0(ShowInSystemExplorerCommandHandler.java:96) at org.eclipse.linuxtools.internal.docker.ui.commands.ShowInSystemExplorerCommandHandler$1.run(ShowInSystemExplorerCommandHandler.java:65) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: java.io.IOException: error=20, Not a directory at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.<init>(UNIXProcess.java:248) at java.lang.ProcessImpl.start(ProcessImpl.java:134) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) ... 5 more {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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 April 2016