June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22674) Refresh handler throws NPE when no active part are selected

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22674?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22674: ------------------------------------ {code} ENTRY org.eclipse.ui 4 0 2016-06-29 11:10:55.991 !MESSAGE Unhandled event loop exception !STACK 0 org.eclipse.e4.core.di.InjectionException: java.lang.NullPointerException at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:64) at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:282) at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:264) 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:494) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:488) at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:433) at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:454) at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem$3.handleEvent(AbstractContributionItem.java:482) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4410) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4228) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3816) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) 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:388) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.__invoke(DelegatingMethodAccessorImpl.java:43) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java) at java.lang.reflect.Method.invoke(Method.java:498) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610) at org.eclipse.equinox.launcher.Main.run(Main.java:1519) at org.eclipse.equinox.launcher.Main.main(Main.java:1492) Caused by: java.lang.NullPointerException at org.jboss.tools.openshift.internal.ui.handler.RefreshResourceHandler.execute(RefreshResourceHandler.java:39) 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.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.__invoke(DelegatingMethodAccessorImpl.java:43) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java) at java.lang.reflect.Method.invoke(Method.java:498) at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54) ... 39 more {code} > Refresh handler throws NPE when no active part are selected > ----------------------------------------------------------- > > Key: JBIDE-22674 > URL: https://issues.jboss.org/browse/JBIDE-22674 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Fix For: 4.4.1.AM2 > > > EXEC: start Eclipse but don't select any part > EXEC: unfold an OS3 connection > EXEC: fill the credentials dialog > EXEC: Refresh the OS3 connection > ASSERT: the refresh handler throws NPE in the Eclipse log -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22674) Refresh handler throws NPE when no active part are selected

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-22674: ---------------------------------- Summary: Refresh handler throws NPE when no active part are selected Key: JBIDE-22674 URL: https://issues.jboss.org/browse/JBIDE-22674 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.0.Final Reporter: Jeff MAURY Fix For: 4.4.1.AM2 EXEC: start Eclipse but don't select any part EXEC: unfold an OS3 connection EXEC: fill the credentials dialog EXEC: Refresh the OS3 connection ASSERT: the refresh handler throws NPE in the Eclipse log -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22603) Sometimes multiple OpenShift watch managers are periodically created and finished

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22603?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22603: ------------------------------------ The rule is that there is one job per Openshift project and per resource type. It seems jobs are sleeping but are respawed because the WebSocket seems to be closed by Openshift on the remote side. I diud not manage to reproduce it because I can't see the jobs in the progress view but I activated the traces for the openshift.core plugin so I can see all related activity > Sometimes multiple OpenShift watch managers are periodically created and finished > --------------------------------------------------------------------------------- > > Key: JBIDE-22603 > URL: https://issues.jboss.org/browse/JBIDE-22603 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Assignee: Jeff MAURY > Priority: Critical > Labels: explorer, openshift_v3 > Fix For: 4.4.x > > Attachments: watchers.png > > > Sometimes when I am working with OpenShift toolings, there are created multiple OpenShift Watch Managers which are getting finished, disappearing from Progress view and another new ones are created and this repeats nonstop. Sometimes there are 2-3 running, sometimes even more. I am working with openshift-dev user, where is visible default project (still, until patch in upstream get effect) and my own project with application created from eap 6.4 basic s2i template. > !watchers.png! > It would not be a problem but I have a hunch it is the problem breaking automatic update of OpenShift explorer view to reflect current state and existence of resources on OpenShift server. E.g. under a service there is build table visible all the time and no application pod is shown, even build is finished and there is an application pod running on OpenShift. Another example when it is not working is when I am scaling application up/down - it does not reflect real amount of application pods. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21745) Unable to download EAP 7 Beta runtime using username without "@redhat.com"

by David Hladky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21745?page=com.atlassian.jira.plugi... ] David Hladky commented on JBIDE-21745: -------------------------------------- Thank you for reporting the issue. The problem is with the registration form. The user name used to be identical with the e-mail, however now the user name is generated from e-mail and differs and the e-mail is used only as an attribute of the account. I created ORG-3408. > Unable to download EAP 7 Beta runtime using username without "@redhat.com" > -------------------------------------------------------------------------- > > Key: JBIDE-21745 > URL: https://issues.jboss.org/browse/JBIDE-21745 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.0.Final, 4.3.1.CR1 > Environment: JBDS 9.1.0.CR1, JBDS 9.0.0.GA > Reporter: Radim Hopp > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.x > > > Trying to download EAP 7 Beta using login without "@redhat.com" fails on license agreement page. > Instead of license agreement being displayed, just message saying "It is no longer possible to accept terms and conditions in the wizard. Please, use following link instead!" is shown. Given link redirects to Red Hat Developers portal login. After successful login, message is shown: > {noformat} > You Entered All Necessary Information > Thank you for filling all necessary information. Now you can go back to Eclipse and retry your download of /jboss-eap-7.0.0.Beta.zip. > {noformat} > But even after that I'm unable to download that runtime with the same credentials. > Using login with "@redhat.com" I'm able to download the runtime. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22608) Support scenario when cdk is stopped from cli and then in devstudio

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22608?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22608: --------------------------------------- [~rob.stryker], ok, it works now on first attempt in devstudio 10 and cdk 2.1. Strange. Of course I wouldn't have reported this if I hadn't seen it :) Second time I tried with the shared folder Vagrantfile: 1. Start cdk in cli 2. Start adapter - is marked as started 3. Stop cdk in cli 4. Now I wanted to stop the adapter - but the stop button is displayed. Any idea why that's happening, [~rob.stryker]? The only button that is enabled now is Restart. (And the status is Started.) > Support scenario when cdk is stopped from cli and then in devstudio > ------------------------------------------------------------------- > > Key: JBIDE-22608 > URL: https://issues.jboss.org/browse/JBIDE-22608 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.4.0.Final > Reporter: Martin Malina > Assignee: Rob Stryker > > Assume your cdk is started and it's shown as started in devstudio, now what if you stop cdk from cli for whatever reason? Currently the tooling can't handle such situation. > If you then try to stop cdk in devstudio, you get an error pop-up: > Server Container Development Environment failed to stop. > And the console will just say: > ==> default: VM not created. Moving on... > But most importantly, the server adapter will stay in the Started state. > We should probably support this scenario - it's quite likely that it will happen to users. > Right now there are several ways out of this situation: > a) Start cdk from cli again and everything will probably work as expected > b) Restart your IDE > So I suggest we improve the tooling in such a way that when you stop cdk, it will be able to detect that it's actually not running and just change the state to Stopped. It may be still ok to pop up the error saying it failed to stop. But at least you can now start it again from the IDE. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3567) Offline install instructions are very unclear

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBDS-3567?page=com.atlassian.jira.plugin.... ] Misha Ali updated JBDS-3567: ---------------------------- Fix Version/s: 10.0.0.GA > Offline install instructions are very unclear > --------------------------------------------- > > Key: JBDS-3567 > URL: https://issues.jboss.org/browse/JBDS-3567 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: documentation > Affects Versions: 9.0.0.GA > Reporter: Mustafa Musaji > Assignee: Misha Ali > Fix For: 10.0.0.GA > > > I came across this - https://access.redhat.com/articles/1367643. I'm puzzled by the instructions on here and what this page is meant to do. > Firstly there's no mention at all of downloading the ZIP from the CSP. https://access.redhat.com/jbossnetwork/restricted/listSoftware.html?produ... > I don't know what the groovy stuff is meant to do, installing and setting up a local maven repo is not in the scope of a JBDS set up but I believe either way it's wrong for this page. > Part 2 talks about "You can install the JBoss and third-party plug-ins listed in JBoss Central in offline mode using the JBoss Central Site .zip file" but then doesn't mention where to download these zips (CSP). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3567) Offline install instructions are very unclear

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBDS-3567?page=com.atlassian.jira.plugin.... ] Misha Ali closed JBDS-3567. --------------------------- Resolution: Done > Offline install instructions are very unclear > --------------------------------------------- > > Key: JBDS-3567 > URL: https://issues.jboss.org/browse/JBDS-3567 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: documentation > Affects Versions: 9.0.0.GA > Reporter: Mustafa Musaji > Assignee: Misha Ali > Fix For: 10.0.0.GA > > > I came across this - https://access.redhat.com/articles/1367643. I'm puzzled by the instructions on here and what this page is meant to do. > Firstly there's no mention at all of downloading the ZIP from the CSP. https://access.redhat.com/jbossnetwork/restricted/listSoftware.html?produ... > I don't know what the groovy stuff is meant to do, installing and setting up a local maven repo is not in the scope of a JBDS set up but I believe either way it's wrong for this page. > Part 2 talks about "You can install the JBoss and third-party plug-ins listed in JBoss Central in offline mode using the JBoss Central Site .zip file" but then doesn't mention where to download these zips (CSP). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22606) Document go_offline.groovy usage

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22606?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-22606. --------------------------------- Fix Version/s: 4.4.1.AM1 Resolution: Done > Document go_offline.groovy usage > -------------------------------- > > Key: JBIDE-22606 > URL: https://issues.jboss.org/browse/JBIDE-22606 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: project-examples > Affects Versions: 4.4.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.4.1.AM1 > > > The go_offline.groovy scripts currently lacks a detailed documentation, most notably on the example descriptor format requirements, we ought to fix that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22606) Document go_offline.groovy usage

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22606?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-22606: ------------------------------------- Here's some doc on the go_offline.groovy script usage: https://github.com/jbosstools/jbosstools-website/blob/master/documentatio... > Document go_offline.groovy usage > -------------------------------- > > Key: JBIDE-22606 > URL: https://issues.jboss.org/browse/JBIDE-22606 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: project-examples > Affects Versions: 4.4.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > > The go_offline.groovy scripts currently lacks a detailed documentation, most notably on the example descriptor format requirements, we ought to fix that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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 Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22274?page=com.atlassian.jira.plugi... ] Jeff Johnston updated JBIDE-22274: ---------------------------------- Sprint: devex #116 June 2016 > 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, upstream > Affects Versions: 4.4.0.Alpha1 > Environment: JBDS 10.0.0.Alpha1-v20160428-0509-B5247 > Reporter: Radim Hopp > Assignee: Jeff Johnston > 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, 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 June 2016