April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21451) Application wizard: No projects nor server templates when launched from explorer context menu

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21451?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21451. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5255. > Application wizard: No projects nor server templates when launched from explorer context menu > --------------------------------------------------------------------------------------------- > > Key: JBIDE-21451 > URL: https://issues.jboss.org/browse/JBIDE-21451 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: empty_project.png > > > Opening a New OpenShift application wizard via context menu of a project makes wizard not usable, because project is not shown and also no templates are available. > !empty_project.png! > This is happening if previously a connection having the project where context menu were opened was used to create a new Server adapter, or at least it passed New Server adapter wizard beyond the page with a connection. > Stack trace: > {code} > org.eclipse.e4.core.di.InjectionException: org.jboss.tools.openshift.core.connection.ConnectionNotFoundException: Unable to find the connection for a Project named someproject > 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.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:799) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:675) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:659) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:592) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430) > 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) > at org.eclipse.equinox.launcher.Main.main(Main.java:1488) > Caused by: org.jboss.tools.openshift.core.connection.ConnectionNotFoundException: Unable to find the connection for a Project named someproject > at org.jboss.tools.openshift.core.connection.ConnectionsRegistryUtil.getConnectionFor(ConnectionsRegistryUtil.java:41) > at org.jboss.tools.openshift.internal.ui.handler.NewProjectHandler.execute(NewProjectHandler.java:44) > 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.GeneratedMethodAccessor81.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) > ... 38 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21524) Explorer, Servers view: Add deployment view to OpenShift v3 explorer

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21524?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21524. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5255. > Explorer, Servers view: Add deployment view to OpenShift v3 explorer > -------------------------------------------------------------------- > > Key: JBIDE-21524 > URL: https://issues.jboss.org/browse/JBIDE-21524 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: explorer, openshift_deployment_view, openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: 2015-10-13 19.03.bmml, 2015-10-13 19.03.png, Console of 'App' with the pieces wired.png, Initial deployment view.png, Pipeline view mockup.bmml, Pipeline view mockup.png > > > Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console > Ref: https://trello.com/c/UybD1Lgx/58-8-as-an-eclipse-user-i-would-like-a-logi... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21459) Server adapter wizard: Improve source path validation

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21459?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21459. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5255. > Server adapter wizard: Improve source path validation > ----------------------------------------------------- > > Key: JBIDE-21459 > URL: https://issues.jboss.org/browse/JBIDE-21459 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter_wizard > Fix For: 4.4.0.Alpha1 > > > First point: In New OpenShift 3 server adapter wizard there is a text label for Source path. Currently there is only not null validation, if there is no path, next button is disabled. Because the path filled in this text widget is local, it would be nice if there would be simple validation of existence of directory described in this text widget. > Second point: validation message shown in header for empty source path is same as for the pod path "Please provide a path to deploy to on the pod.", what is not correct. This message should be different. > Third point: it would be nice to have an asterisks on required fields, such as pod or source path. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3850) Test code coverage console report for platform installer unit tests

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/JBDS-3850?page=com.atlassian.jira.plugin.... ] Pavol Pitonak updated JBDS-3850: -------------------------------- Fix Version/s: 10.0.0.Alpha2 (was: 10.0.0.Alpha1) > Test code coverage console report for platform installer unit tests > ------------------------------------------------------------------- > > Key: JBDS-3850 > URL: https://issues.jboss.org/browse/JBDS-3850 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Denis Golovin > Assignee: Pavol Pitonak > Labels: Havoc > Fix For: 10.0.0.Alpha2 > > Attachments: code_coverage_unit.png > > > Would be good to have code coverage report for unit tests to see how reliable tests are -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22262) Only OpenShift 3 connections should be listed when opening Deploy Image to OpenShift wizard

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22262?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22262. --------------------------------- Resolution: Done Yeah, fix works nice. Thanks. Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5255. > Only OpenShift 3 connections should be listed when opening Deploy Image to OpenShift wizard > ------------------------------------------------------------------------------------------- > > Key: JBIDE-22262 > URL: https://issues.jboss.org/browse/JBIDE-22262 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: docker, openshift_v3 > Fix For: 4.4.0.Alpha1 > > > When opening Deploy Image to OpenShift wizard from context menu of a docker image, connection dialog is opened at first. There is available OpenShift 3 type of server as well as OpenShift 2 server. There should be available only OpenShift 3 server type and listed only OpenShift 3 connections. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22174) Deploy Image to OpenShift wizard could respect selected connection and project from OpenShift Explorer

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22174?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22174. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5255. > Deploy Image to OpenShift wizard could respect selected connection and project from OpenShift Explorer > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-22174 > URL: https://issues.jboss.org/browse/JBIDE-22174 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha1 > > > When opening Deploy Image to OpenShift wizard via context menu of a docker image in Docker Explorer, selected project (or a connection if no project under a connection is selected) should be selected in combo in the wizard. At the moment, if there is precisely 1 connection, it is selected (if there are more connections, no connection is selected and following steps is not reachable) and if there is precisely 1 project, that one is selected (if there are more projects, no project is selected). This could be refined a bit. In case of selection would be the selected one in combo. In case of existence of more connections/projects and no selection, maybe the first one listed could be selected (but this is probably personal preference, maybe it is not a good idea). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-731) Update: JBDS IS 9.0.0 GA Install Guide

by Supriya Bharadwaj (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-731?page=com.atlassian.jira.plug... ] Supriya Bharadwaj reassigned TOOLSDOC-731: ------------------------------------------ Assignee: Andrej Podhradsky (was: Supriya Bharadwaj) > Update: JBDS IS 9.0.0 GA Install Guide > -------------------------------------- > > Key: TOOLSDOC-731 > URL: https://issues.jboss.org/browse/TOOLSDOC-731 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: Installation Guide > Reporter: Supriya Bharadwaj > Assignee: Andrej Podhradsky > Fix For: 9.0.0 > > -- 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 Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22274?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22274: -------------------------------- Fix Version/s: 4.4.x > 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 > Fix For: 4.4.x > > > 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

[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 Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22274?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-22274: ------------------------------------- [~rhopp] can you open a bug upstream, at bugs.eclipse.org, please? > 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

[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: ------------------------------------- replying to myself, it returns: {quote}oc v1.2.0-rc2{quote} [~jeffmaury] the version parsing seems off > 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

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