March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3608) update devstudio.redhat.com branding

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3608?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3608: -------------------------------------- Fix Version/s: (was: 9.1.0.CR1) > update devstudio.redhat.com branding > ------------------------------------ > > Key: JBDS-3608 > URL: https://issues.jboss.org/browse/JBDS-3608 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: website > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Blocker > Fix For: 10.0.0.Alpha1 > > > update branding for developers.redhat.com -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3610) update docs to use new name

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3610?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3610: ------------------------------------------- moved out from 9.1 to 10.0 > update docs to use new name > --------------------------- > > Key: JBDS-3610 > URL: https://issues.jboss.org/browse/JBDS-3610 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: documentation > Reporter: Max Rydahl Andersen > Priority: Optional > Fix For: 10.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3609) update splashscreen, about gfx, start icon for developers.redhat.com

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3609?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3609: -------------------------------------- Fix Version/s: 10.0.0.Alpha1 (was: 9.1.0.CR1) > update splashscreen, about gfx, start icon for developers.redhat.com > -------------------------------------------------------------------- > > Key: JBDS-3609 > URL: https://issues.jboss.org/browse/JBDS-3609 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: build, installer, p2-product > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Blocker > Fix For: 10.0.0.Alpha1 > > > update splashscreen, about gfx, start icon for developers.redhat.com -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3609) update splashscreen, about gfx, start icon for developers.redhat.com

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3609?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3609: ------------------------------------------- moved out past 9.1 > update splashscreen, about gfx, start icon for developers.redhat.com > -------------------------------------------------------------------- > > Key: JBDS-3609 > URL: https://issues.jboss.org/browse/JBDS-3609 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: build, installer, p2-product > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Blocker > Fix For: 10.0.0.Alpha1 > > > update splashscreen, about gfx, start icon for developers.redhat.com -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3612) Define new names for studio

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3612?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3612: -------------------------------------- Fix Version/s: (was: 9.1.0.CR1) > Define new names for studio > --------------------------- > > Key: JBDS-3612 > URL: https://issues.jboss.org/browse/JBDS-3612 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer, p2-product > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 10.0.0.Alpha1 > > > Issue to outline names for final products - blocks completion of any branding work. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3610) update docs to use new name

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3610?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3610: -------------------------------------- Fix Version/s: 10.0.0.Alpha1 (was: 9.1.0.CR1) > update docs to use new name > --------------------------- > > Key: JBDS-3610 > URL: https://issues.jboss.org/browse/JBDS-3610 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: documentation > Reporter: Max Rydahl Andersen > Priority: Optional > Fix For: 10.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3612) Define new names for studio

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3612?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3612: ------------------------------------------- not happening in 9.1, moved to 10.0 > Define new names for studio > --------------------------- > > Key: JBDS-3612 > URL: https://issues.jboss.org/browse/JBDS-3612 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer, p2-product > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 10.0.0.Alpha1 > > > Issue to outline names for final products - blocks completion of any branding work. -- 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 closed JBIDE-21920. --------------------------------- Verified on nightly build of JBT with OpenShift plugin build B242. > 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 > Assignee: Fred Bricon > Priority: Blocker > Labels: oc_binary, 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 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 resolved JBIDE-21938. ----------------------------------- Resolution: Done > 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] (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: ---------------------------------- Fix Version/s: (was: 4.4.0.Alpha1) > 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 > Assignee: Fred Bricon > Priority: Blocker > Labels: oc_binary, 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 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

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