July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20371) Need a link to download/install oc binary

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20371?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20371: -------------------------------- Description: Currently there's no indication on how to get access and install the oc binary, required for at least using the port forwarding feature. We can not expect users to manually build it. Best case scenario, eclipse provides a way to install it Worst case scenario, it links to https://github.com/openshift/origin/blob/master/CONTRIBUTING.adoc#downloa... was: Currently there's no indication on how to get access and install the oc binary. We can not expect users to manually build it. Best case scenario, eclipse provides a way to install it Worst case scenario, it links to https://github.com/openshift/origin/blob/master/CONTRIBUTING.adoc#downloa... > Need a link to download/install oc binary > ----------------------------------------- > > Key: JBIDE-20371 > URL: https://issues.jboss.org/browse/JBIDE-20371 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Fred Bricon > Labels: openshift_v3 > Fix For: 4.3.0.CR1 > > > Currently there's no indication on how to get access and install the oc binary, required for at least using the port forwarding feature. We can not expect users to manually build it. > Best case scenario, eclipse provides a way to install it > Worst case scenario, it links to https://github.com/openshift/origin/blob/master/CONTRIBUTING.adoc#downloa... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20371) Need a link to download/install oc binary

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20371?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20371: -------------------------------- Fix Version/s: 4.3.0.CR1 > Need a link to download/install oc binary > ----------------------------------------- > > Key: JBIDE-20371 > URL: https://issues.jboss.org/browse/JBIDE-20371 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Fred Bricon > Labels: openshift_v3 > Fix For: 4.3.0.CR1 > > > Currently there's no indication on how to get access and install the oc binary. We can not expect users to manually build it. > Best case scenario, eclipse provides a way to install it > Worst case scenario, it links to https://github.com/openshift/origin/blob/master/CONTRIBUTING.adoc#downloa... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20371) Need a link to download/install oc binary

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-20371: ----------------------------------- Summary: Need a link to download/install oc binary Key: JBIDE-20371 URL: https://issues.jboss.org/browse/JBIDE-20371 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.3.0.Beta2 Reporter: Fred Bricon Currently there's no indication on how to get access and install the oc binary. We can not expect users to manually build it. Best case scenario, eclipse provides a way to install it Worst case scenario, it links to https://github.com/openshift/origin/blob/master/CONTRIBUTING.adoc#downloa... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20371) Need a link to download/install oc binary

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20371?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20371: -------------------------------- Labels: openshift_v3 (was: ) > Need a link to download/install oc binary > ----------------------------------------- > > Key: JBIDE-20371 > URL: https://issues.jboss.org/browse/JBIDE-20371 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Fred Bricon > Labels: openshift_v3 > > Currently there's no indication on how to get access and install the oc binary. We can not expect users to manually build it. > Best case scenario, eclipse provides a way to install it > Worst case scenario, it links to https://github.com/openshift/origin/blob/master/CONTRIBUTING.adoc#downloa... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19850) As a user I want to easily set up port forwarding for my application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19850?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19850: ------------------------------------------ [~jcantrill] do I get it right that this means that the latest binaries cannot work against stg, stg needs an update? > As a user I want to easily set up port forwarding for my application > -------------------------------------------------------------------- > > Key: JBIDE-19850 > URL: https://issues.jboss.org/browse/JBIDE-19850 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Priority: Blocker > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.3.0.CR1 > > Attachments: hello_world_template.json > > > As a user I want to be able to easily set up port forwarding to my application > Test by: > # Start OpenShift > # Create app from attached template > # Right Click on "Hello-world Pod" > Forward Ports > # Check find open ports > # Start Port forwarding > # In a terminal "curl localhost:<assigned local port>" > # Expect "Hello OpenShift" -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20324) Unhandled event loop exception when trying to delete a deployment on a server

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20324?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20324: ------------------------------------------ The simple fix would be to add a null-check to avoid the exception, but my bigger concern is that somehow my (openshift) handlers are active when the servers view is focused? This would be the cause for a few additional problems we didnt discover yet. I believe that the proper fix is to make sure my handlers are not executed > Unhandled event loop exception when trying to delete a deployment on a server > ----------------------------------------------------------------------------- > > Key: JBIDE-20324 > URL: https://issues.jboss.org/browse/JBIDE-20324 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.3.0.Beta2 > Reporter: Martin Malina > Assignee: Andre Dietisheim > Attachments: remove-deployment.png > > > When I click a module (e.g. dynamic web project) deployed to a running server and then hit the Del key on my keyboard, I will always get an exception in the Error Log: > {code} > Unhandled event loop exception > org.eclipse.e4.core.di.InjectionException: java.lang.NullPointerException > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:68) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) > at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152) > at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) > at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.executeCommand(KeyBindingDispatcher.java:286) > at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.press(KeyBindingDispatcher.java:507) > at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.processKeyEvent(KeyBindingDispatcher.java:558) > at org.eclipse.e4.ui.bindings.keys.OutOfOrderListener.handleEvent(OutOfOrderListener.java:72) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4230) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1499) > at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1528) > at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1524) > at org.eclipse.swt.widgets.Tree.sendKeyEvent(Tree.java:2592) > at org.eclipse.swt.widgets.Control.keyDown(Control.java:2402) > at org.eclipse.swt.widgets.Composite.keyDown(Composite.java:607) > at org.eclipse.swt.widgets.Tree.keyDown(Tree.java:1991) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5694) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) > at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:227) > at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2130) > at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2337) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5756) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) > at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5193) > at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5342) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) > at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3695) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608) > at org.eclipse.equinox.launcher.Main.run(Main.java:1515) > Caused by: java.lang.NullPointerException > at org.jboss.tools.openshift.internal.common.ui.command.RemoveConnectionHandler$1.toString(RemoveConnectionHandler.java:44) > at org.jboss.tools.openshift.internal.common.ui.command.RemoveConnectionHandler$1.toString(RemoveConnectionHandler.java:1) > at org.jboss.tools.openshift.common.core.utils.StringUtils.toString(StringUtils.java:69) > at org.jboss.tools.openshift.internal.common.ui.command.RemoveConnectionHandler.execute(RemoveConnectionHandler.java:38) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > at sun.reflect.GeneratedMethodAccessor85.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) > ... 55 more > {code} > This looks like an upstream bug :-\ Let me know if I should report this. > Note that this probably only happens on Mac - Jirka Peterka tried this for me on Linux and it worked fine. > Also, one indicator of the problem is that when you right-click a deployed module in the Servers view, you can't see the shortcut there next to Remove. > !remove-deployment.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19850) As a user I want to easily set up port forwarding for my application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19850?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-19850 at 7/23/15 6:15 PM: ------------------------------------------------------------------- If I use *console.stg.openshift.com* and do all the setup and portforwarding in the cmd-line I get the exact same error as I captured in Eclipse further up in the comments: {code} [adietish@localhost origin]$ oc port-forward -p hello-openshift 8181:8080 error: Error upgrading connection: User "adietish(a)redhat.com" cannot create pods/portforward in project "project036" {code} It very much looks like there's a problem in the server or "oc" binary that we cant fix for now. We're releasing 4.3.0.Beta2 with this broken unfortunately. Postponing to 4.3.0.CR1 was (Author: adietish): If I do all the setup and portforwarding in the cmd-line I get the exact same error as I captured in Eclipse further up in the comments: {code} [adietish@localhost origin]$ oc port-forward -p hello-openshift 8181:8080 error: Error upgrading connection: User "adietish(a)redhat.com" cannot create pods/portforward in project "project036" {code} It very much looks like there's a problem in the server or "oc" binary that we cant fix for now. We're releasing 4.3.0.Beta2 with this broken unfortunately. Postponing to 4.3.0.CR1 > As a user I want to easily set up port forwarding for my application > -------------------------------------------------------------------- > > Key: JBIDE-19850 > URL: https://issues.jboss.org/browse/JBIDE-19850 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Priority: Blocker > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.3.0.CR1 > > Attachments: hello_world_template.json > > > As a user I want to be able to easily set up port forwarding to my application > Test by: > # Start OpenShift > # Create app from attached template > # Right Click on "Hello-world Pod" > Forward Ports > # Check find open ports > # Start Port forwarding > # In a terminal "curl localhost:<assigned local port>" > # Expect "Hello OpenShift" -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19850) As a user I want to easily set up port forwarding for my application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19850?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-19850 at 7/23/15 6:14 PM: ------------------------------------------------------------------- If I do all the setup and portforwarding in the cmd-line I get the exact same error as I captured in Eclipse further up in the comments: {code} [adietish@localhost origin]$ oc port-forward -p hello-openshift 8181:8080 error: Error upgrading connection: User "adietish(a)redhat.com" cannot create pods/portforward in project "project036" {code} It very much looks like there's a problem in the server or "oc" binary that we cant fix for now. We're releasing 4.3.0.Beta2 with this broken unfortunately. Postponing to 4.3.0.CR1 was (Author: adietish): It very much looks like there's a problem in the server or "oc" binary that we cant fix for now. We're releasing 4.3.0.Beta2 with this broken unfortunately. Postponing to 4.3.0.CR1 > As a user I want to easily set up port forwarding for my application > -------------------------------------------------------------------- > > Key: JBIDE-19850 > URL: https://issues.jboss.org/browse/JBIDE-19850 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Priority: Blocker > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.3.0.CR1 > > Attachments: hello_world_template.json > > > As a user I want to be able to easily set up port forwarding to my application > Test by: > # Start OpenShift > # Create app from attached template > # Right Click on "Hello-world Pod" > Forward Ports > # Check find open ports > # Start Port forwarding > # In a terminal "curl localhost:<assigned local port>" > # Expect "Hello OpenShift" -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16379) Using symbolic links in the workspace path causes an infinite loop for m2e builder

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16379?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-16379: ---------------------------------------- OK. But this is still an issue. We should report it to bugzilla. Could you do it please? > Using symbolic links in the workspace path causes an infinite loop for m2e builder > ---------------------------------------------------------------------------------- > > Key: JBIDE-16379 > URL: https://issues.jboss.org/browse/JBIDE-16379 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, upstream > Affects Versions: 4.2.0.Alpha1 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > Fix For: 4.3.x > > > See JBIDE-16286 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16379) Using symbolic links in the workspace path causes an infinite loop for m2e builder

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16379?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-16379: --------------------------------------- No, we don't. See https://issues.jboss.org/browse/JBIDE-16379?focusedCommentId=13011208&pag... > Using symbolic links in the workspace path causes an infinite loop for m2e builder > ---------------------------------------------------------------------------------- > > Key: JBIDE-16379 > URL: https://issues.jboss.org/browse/JBIDE-16379 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, upstream > Affects Versions: 4.2.0.Alpha1 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > Fix For: 4.3.x > > > See JBIDE-16286 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 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 July 2015