March 2016 - jbosstools-issues - Jboss List Archives

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

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21938: ------------------------------------- Summary: Cannot use features which are using oc binary Key: JBIDE-21938 URL: https://issues.jboss.org/browse/JBIDE-21938 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.CR1 Reporter: Marián Labuda Assignee: Fred Bricon Priority: Blocker Fix For: 4.3.1.CR1, 4.4.0.Alpha1 After latest update of nightly JBT I am not able to get logs from pods(/builds) or use port forwarding . 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. But when using port forwading, there is an error with following stack {code} com.openshift.restclient.capability.resources.LocationNotFoundException: The OpenShift 'oc' binary location was not specified. Set the property openshift.restclient.oc.location at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.getOpenShiftBinaryLocation(AbstractOpenShiftBinaryCapability.java:189) at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.start(AbstractOpenShiftBinaryCapability.java:123) at com.openshift.internal.restclient.capability.resources.OpenShiftBinaryPortForwarding.forwardPorts(OpenShiftBinaryPortForwarding.java:66) at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:128) at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:1) at com.openshift.internal.restclient.model.KubernetesResource.accept(KubernetesResource.java:91) at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils.startPortForwarding(PortForwardingUtils.java:124) at org.jboss.tools.openshift.internal.ui.portforwading.PortForwardingWizardModel.startPortForwarding(PortForwardingWizardModel.java:110) at org.jboss.tools.openshift.internal.ui.portforwading.PortForwardingWizardPage$3$1.run(PortForwardingWizardPage.java:157) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

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

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21938?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21938: ---------------------------------- Fix Version/s: (was: 4.3.1.CR1) > Cannot use features which are using oc binary > --------------------------------------------- > > Key: JBIDE-21938 > URL: https://issues.jboss.org/browse/JBIDE-21938 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Blocker > Labels: oc_binary, openshift_v3 > Fix For: 4.4.0.Alpha1 > > > After latest update of nightly JBT I am not able to get logs from pods(/builds) or use port forwarding . 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. > But when using port forwading, there is an error with following stack > {code} > com.openshift.restclient.capability.resources.LocationNotFoundException: The OpenShift 'oc' binary location was not specified. Set the property openshift.restclient.oc.location > at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.getOpenShiftBinaryLocation(AbstractOpenShiftBinaryCapability.java:189) > at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.start(AbstractOpenShiftBinaryCapability.java:123) > at com.openshift.internal.restclient.capability.resources.OpenShiftBinaryPortForwarding.forwardPorts(OpenShiftBinaryPortForwarding.java:66) > at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:128) > at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:1) > at com.openshift.internal.restclient.model.KubernetesResource.accept(KubernetesResource.java:91) > at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils.startPortForwarding(PortForwardingUtils.java:124) > at org.jboss.tools.openshift.internal.ui.portforwading.PortForwardingWizardModel.startPortForwarding(PortForwardingWizardModel.java:110) > at org.jboss.tools.openshift.internal.ui.portforwading.PortForwardingWizardPage$3$1.run(PortForwardingWizardPage.java:157) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3605) Rebranding to developers.redhat.com

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3605?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3605: -------------------------------------- Fix Version/s: 10.0.0.Alpha1 (was: 9.1.0.CR1) > Rebranding to developers.redhat.com > ----------------------------------- > > Key: JBDS-3605 > URL: https://issues.jboss.org/browse/JBDS-3605 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: installer, p2-product > Reporter: Max Rydahl Andersen > Assignee: Catherine Robson > Priority: Blocker > Fix For: 10.0.0.Alpha1 > > Attachments: about-jbds10.png, header-jbds10-installer.png, RedHatDevelopersStudio_SplashScreen.zip, RedHatDeveloperStudio-Branding_Final_2016-03-16.pdf, RedHatDeveloperStudio_BrandingDeliverables.zip, splash-jbds10.png > > > Developer Studio, Central and any related installers, website content etc. is requested to be rebranded under http://developers.redhat.com. > The visual name will change but for JBDS 9.1 we will not change things that risk breaking functionallity (i.e. changing the binary from jbds to rhds will potentially break update path, ini and p2 update mechanisms) > Thus changing about screen, splash screens etc. are the target - more deeper rebranding will be done in future and on a case-by-base basis if at all necessary. > > This jira will be the epic where we add related issues. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3605) Rebranding to developers.redhat.com

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3605?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3605: ------------------------------------------- rebrand have been postponed to near summit - thus moving this off 9.1 to 10.0. > Rebranding to developers.redhat.com > ----------------------------------- > > Key: JBDS-3605 > URL: https://issues.jboss.org/browse/JBDS-3605 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: installer, p2-product > Reporter: Max Rydahl Andersen > Assignee: Catherine Robson > Priority: Blocker > Fix For: 10.0.0.Alpha1 > > Attachments: about-jbds10.png, header-jbds10-installer.png, RedHatDevelopersStudio_SplashScreen.zip, RedHatDeveloperStudio-Branding_Final_2016-03-16.pdf, RedHatDeveloperStudio_BrandingDeliverables.zip, splash-jbds10.png > > > Developer Studio, Central and any related installers, website content etc. is requested to be rebranded under http://developers.redhat.com. > The visual name will change but for JBDS 9.1 we will not change things that risk breaking functionallity (i.e. changing the binary from jbds to rhds will potentially break update path, ini and p2 update mechanisms) > Thus changing about screen, splash screens etc. are the target - more deeper rebranding will be done in future and on a case-by-base basis if at all necessary. > > This jira will be the epic where we add related issues. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3701) Add check for an existing Java to find if it is JRE or JDK

by Jan Richter (JIRA)

Jan Richter created JBDS-3701: --------------------------------- Summary: Add check for an existing Java to find if it is JRE or JDK Key: JBDS-3701 URL: https://issues.jboss.org/browse/JBDS-3701 Project: Developer Studio (JBoss Developer Studio) Issue Type: Enhancement Components: installer Affects Versions: 9.1.0.CR1 Reporter: Jan Richter Assignee: Denis Golovin JBDS will run on both, but in order to develop something the user needs a JDK. The detection/selection will allow using JRE distribution of Java without even a warning. We should find out what kind of Java the user has selected and at least display a warning if it is not JDK (or just not allow JRE). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21930) Liberalize some astools API for re-use

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21930?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21930. --------------------------------- > Liberalize some astools API for re-use > -------------------------------------- > > Key: JBIDE-21930 > URL: https://issues.jboss.org/browse/JBIDE-21930 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 4.3.1.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.1.CR1 > > > In order to allow openshift to use (but also override pieces of) our incremental deployment, we must liberalize a few methods from private to protected, and add a few superclasses for extending to avoid code duplication. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21935) resue flow in clone wizard is ambigious

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21935?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21935: ---------------------------------- Labels: application_wizard openshift_v3 (was: ) > resue flow in clone wizard is ambigious > --------------------------------------- > > Key: JBIDE-21935 > URL: https://issues.jboss.org/browse/JBIDE-21935 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Max Rydahl Andersen > Labels: application_wizard, openshift_v3 > > continuation of JBIDE-14828: > with the intended behavior explained then lets make that visible to the user: > a) don't hide/show controls in a wizard, enable/disable them. > b) The "Reuse" is ambiguous, i.e. I read it as the clone will happen into this folder, not that it will do exactly the opposite of what the wizard says (not clone). I suggest something like "Do not clone - reuse existing folder". > c) if not already there, add a check that what is inside the folder is actually a clone of what we are trying to clone. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21937) Application Wizard: if git clone directory already exist i cannot do anything

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21937: ------------------------------------- Summary: Application Wizard: if git clone directory already exist i cannot do anything Key: JBIDE-21937 URL: https://issues.jboss.org/browse/JBIDE-21937 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Reporter: Andre Dietisheim Assignee: Rob Stryker Fix For: 4.3.1.CR1, 4.4.0.Alpha1 steps to reproduce: # EXEC: create and/or import some appliaction from OpenShift to your local workspace using the application/import wizard # EXEC: once you have the project imported to your workspace, delete it # EXEC: once it is deleted, go and try to re-import the very same application Result: The 3rd wizard page errors on the git cloning destination. You're told that the destination folder already exists within the clone destination folder. The only way out currently is to choose a different clone destination folder. !application-folder-already-exists.png! Expected: It would help a lot if wizard would allow you to overwrite the existing destination. The wizard could also check if the given folder holds a prior clone and then allow one to "reuse" this folder. The given folder would then simply get imported to Eclipse and we'd fetch instead of cloning. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-14828) Application Wizard: if git clone directory already exist i cannot do anything

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14828?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-14828: ---------------------------------- Fix Version/s: (was: 4.4.0.Alpha1) > Application Wizard: if git clone directory already exist i cannot do anything > ----------------------------------------------------------------------------- > > Key: JBIDE-14828 > URL: https://issues.jboss.org/browse/JBIDE-14828 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Labels: application_wizard > Fix For: 4.3.1.CR1 > > Attachments: application-folder-already-exists.png > > > steps to reproduce: > # EXEC: create and/or import some appliaction from OpenShift to your local workspace using the application/import wizard > # EXEC: once you have the project imported to your workspace, delete it > # EXEC: once it is deleted, go and try to re-import the very same application > Result: > The 3rd wizard page errors on the git cloning destination. You're told that the destination folder already exists within the clone destination folder. The only way out currently is to choose a different clone destination folder. > !application-folder-already-exists.png! > Expected: > It would help a lot if wizard would allow you to overwrite the existing destination. The wizard could also check if the given folder holds a prior clone and then allow one to "reuse" this folder. The given folder would then simply get imported to Eclipse and we'd fetch instead of cloning. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-14828) Application Wizard: if git clone directory already exist i cannot do anything

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14828?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-14828. --------------------------------- Verified on nightly build of JBT with OpenShift plugin build B240. > Application Wizard: if git clone directory already exist i cannot do anything > ----------------------------------------------------------------------------- > > Key: JBIDE-14828 > URL: https://issues.jboss.org/browse/JBIDE-14828 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Labels: application_wizard > Fix For: 4.3.1.CR1 > > Attachments: application-folder-already-exists.png > > > steps to reproduce: > # EXEC: create and/or import some appliaction from OpenShift to your local workspace using the application/import wizard > # EXEC: once you have the project imported to your workspace, delete it > # EXEC: once it is deleted, go and try to re-import the very same application > Result: > The 3rd wizard page errors on the git cloning destination. You're told that the destination folder already exists within the clone destination folder. The only way out currently is to choose a different clone destination folder. > !application-folder-already-exists.png! > Expected: > It would help a lot if wizard would allow you to overwrite the existing destination. The wizard could also check if the given folder holds a prior clone and then allow one to "reuse" this folder. The given folder would then simply get imported to Eclipse and we'd fetch instead of cloning. -- 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