[JBoss JIRA] (JBIDE-23010) landrush plugin prevents CDK server adapter from starting
by Brian Exelbierd (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23010?page=com.atlassian.jira.plugi... ]
Brian Exelbierd commented on JBIDE-23010:
-----------------------------------------
> We never find out the return code, because the process never completes, because eclipse is still reading the streams, and this prevents vagrant from completing.
A very simple test of mine where I ran a Vagrantfile that had a sleep in the shell init and then manually ran `ps` on my machine shows that, at least for Fedora, vagrant appears to exit even though the streams aren't closed.
I am not sure how this is different under eclipse. I was under the impression from some reading that the waitfor() call was returning after the process exited. I am not a java guru though and may have misinterpreted what I read.
I will keep punching at this from this side too.
> landrush plugin prevents CDK server adapter from starting
> ---------------------------------------------------------
>
> Key: JBIDE-23010
> URL: https://issues.jboss.org/browse/JBIDE-23010
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, upstream
> Affects Versions: 4.4.1.AM3
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Critical
>
> Today I downloaded cdk 2.2.rc1 [1], installed all the vagrant plugins from scratch. And then I first started this from CLI - it wanted password for sudo to set up landrush. (That's another concern I have: How will this work in devstudio? Probably it won't.)
> Then I stopped it, set up in devstudio and start there. Everything looks fine, but the server adapter is stuck at "Starting...".
> This is the console output:
> {code}
> Bringing machine 'default' up with 'virtualbox' provider...
> ==> default: Clearing any previously set forwarded ports...
> ==> default: Clearing any previously set network interfaces...
> ==> default: [landrush] virtualbox requires an additional private network; adding it
> ==> default: [landrush] starting dns server
> ==> default: Preparing network interfaces based on configuration...
> default: Adapter 1: nat
> default: Adapter 2: hostonly
> ==> default: Forwarding ports...
> default: 22 (guest) => 2222 (host) (adapter 1)
> ==> default: Running 'pre-boot' VM customizations...
> ==> default: Booting VM...
> ==> default: Waiting for machine to boot. This may take a few minutes...
> default: SSH address: 127.0.0.1:2222
> default: SSH username: vagrant
> default: SSH auth method: private key
> default: Warning: Remote connection disconnect. Retrying...
> default: Warning: Remote connection disconnect. Retrying...
> default: Warning: Remote connection disconnect. Retrying...
> ==> default: Machine booted and ready!
> ==> default: Registering box with vagrant-registration...
> ==> default: Checking for guest additions in VM...
> default: No guest additions were detected on the base box for this VM! Guest
> default: additions are required for forwarded ports, shared folders, host only
> default: networking, and more. If SSH fails on this machine, please install
> default: the guest additions and repackage the box to continue.
> default:
> default: This is not an error message; everything may continue to work properly,
> default: in which case you may ignore this message.
> ==> default: Setting hostname...
> ==> default: Configuring and enabling network interfaces...
> [landrush] Using eth1 (172.28.128.3)
> ==> default: [landrush] adding machine entry: cdk.vm => 172.28.128.3
> ==> default: [landrush] adding static DNS entry: cdk => cdk.vm
> [landrush] Using eth1 (172.28.128.3)
> [landrush] Host DNS resolver config looks good.
> ==> default: Copying TLS certificates to /Users/rasp/jbossqa/cdk2.2.rc1/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker
> ==> default: Mounting SSHFS shared folder...
> ==> default: Mounting folder via SSHFS: /Users/rasp => /Users/rasp
> ==> default: Checking Mount..
> ==> default: Checking Mount..
> ==> default: Folder Successfully Mounted!
> ==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision`
> ==> default: flag to force provisioning. Provisioners marked to run always will still run.
> ==> default: Running provisioner: shell...
> default: Running: inline script
> ==> default: Running provisioner: shell...
> default: Running: inline script
> ==> default:
> ==> default: Successfully started and provisioned VM with 2 cores and 3072 MB of memory.
> ==> default: To modify the number of cores and/or available memory set the environment variables
> ==> default: VM_CPU respectively VM_MEMORY.
> ==> default:
> ==> default: You can now access the OpenShift console on: https://openshift.cdk:8443/console
> ==> default:
> ==> default: To use OpenShift CLI, run:
> ==> default: $ vagrant ssh
> ==> default: $ oc login
> ==> default:
> ==> default: Configured users are (<username>/<password>):
> ==> default: openshift-dev/devel
> ==> default: admin/admin
> ==> default:
> ==> default: If you have the oc client library on your host, you can also login from your host.
> {code}
> These are my plugins:
> {code}
> $ vagrant plugin list
> landrush (1.1.1)
> - Version Constraint: 1.1.1
> vagrant-registration (1.2.3)
> - Version Constraint: 1.2.3
> vagrant-service-manager (1.3.0)
> - Version Constraint: 1.3.0
> vagrant-share (1.1.5, system)
> vagrant-sshfs (1.2.0)
> - Version Constraint: 1.2.0
> {code}
> [1] http://cdk-builds.usersys.redhat.com/builds/weekly/12-Aug-2016.rc1/
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBDS-3627) Installer needs to help move past lack of t/c signing
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-3627:
-------------------------------------
David, I am using curl -u, please see above.
> Installer needs to help move past lack of t/c signing
> -----------------------------------------------------
>
> Key: JBDS-3627
> URL: https://issues.jboss.org/browse/JBDS-3627
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Reporter: Joshua Wilson
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 10.1.0.AM3
>
> Attachments: Installer-not-signed-tc.PNG
>
>
> DevSuite installer uses "REST services in JBoss Download Manager" explained here https://mojo.redhat.com/docs/DOC-940689.
> DevSuite Intsaller follows the explanation for tc-accepted entry point [code is here|https://github.com/redhat-developer-tooling/developer-platform-insta...]. It uses file from previous CDK release (published in cdn and available through download manager) to do verification:
> 1. that provided credentials are valid;
> 2. that required T&C's are signed.
> There are two major use cases for developers installing DevSuite using Installer:
> 1. Direct download - when developer sign in to developers.redhat.com and download installer himeslf;
> 2. Shared installer - when someone share installer with developers without account.
> There two kind of users involved in those scenarios above:
> 1. New users that must go through registration process;
> 2. Registered users.
> *Direct download*
> For new ones registration process is really simple now. After creating RHD account and downloading installer there is no additional steps to get through installation.
> For already registered users there could be problems related to T&C's and authentication reported here https://issues.jboss.org/browse/RHDENG-579.
> So far there are two kind of problems:
> 1. Users can login and download DevSuite installer, but cannot use the same credentials to install;
> 2. Users that can login in to developers.redhat.com and get request to sign additional T&C's but credentials for the same user in DevSuite Installer reported as invalid when REST tc-accepted entry point is used
> *Shared Download*
> In this scenario new users without account can press Register link, then go through registration process in browser return back to installer and use new account credentials for installation.
> Registered users could need to sign additional T&C's if missing and would be good to show external link to do so. Current entry point tc-accepted does not provide any hints where missing T&C's could be signed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBDS-3627) Installer needs to help move past lack of t/c signing
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ]
Denis Golovin edited comment on JBDS-3627 at 8/17/16 1:19 PM:
--------------------------------------------------------------
https://www.redhat.com/wapps/ugc/register.html does not help, I can create a user and then if I try to use it with res service
{code} curl -u user:password https://developers.redhat.com/download-manager/jdf/file/cdk-2.1.0.zip?wor...
it says: "Please, use a valid user name and password!". After I login to developers.redhat.com account and accept T&C's new account works just fine with jdf download manager links and I have no T&C's related problems.
was (Author: dgolovin):
https://www.redhat.com/wapps/ugc/register.html does not help, I can create a user and then if I try to use it with res service
{code} curl -u user:path https://developers.redhat.com/download-manager/jdf/file/cdk-2.1.0.zip?wor...
it says: "Please, use a valid user name and password!". After I login to developers.redhat.com account and accept T&C's new account works just fine with jdf download manager links and I have no T&C's related problems.
> Installer needs to help move past lack of t/c signing
> -----------------------------------------------------
>
> Key: JBDS-3627
> URL: https://issues.jboss.org/browse/JBDS-3627
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Reporter: Joshua Wilson
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 10.1.0.AM3
>
> Attachments: Installer-not-signed-tc.PNG
>
>
> DevSuite installer uses "REST services in JBoss Download Manager" explained here https://mojo.redhat.com/docs/DOC-940689.
> DevSuite Intsaller follows the explanation for tc-accepted entry point [code is here|https://github.com/redhat-developer-tooling/developer-platform-insta...]. It uses file from previous CDK release (published in cdn and available through download manager) to do verification:
> 1. that provided credentials are valid;
> 2. that required T&C's are signed.
> There are two major use cases for developers installing DevSuite using Installer:
> 1. Direct download - when developer sign in to developers.redhat.com and download installer himeslf;
> 2. Shared installer - when someone share installer with developers without account.
> There two kind of users involved in those scenarios above:
> 1. New users that must go through registration process;
> 2. Registered users.
> *Direct download*
> For new ones registration process is really simple now. After creating RHD account and downloading installer there is no additional steps to get through installation.
> For already registered users there could be problems related to T&C's and authentication reported here https://issues.jboss.org/browse/RHDENG-579.
> So far there are two kind of problems:
> 1. Users can login and download DevSuite installer, but cannot use the same credentials to install;
> 2. Users that can login in to developers.redhat.com and get request to sign additional T&C's but credentials for the same user in DevSuite Installer reported as invalid when REST tc-accepted entry point is used
> *Shared Download*
> In this scenario new users without account can press Register link, then go through registration process in browser return back to installer and use new account credentials for installation.
> Registered users could need to sign additional T&C's if missing and would be good to show external link to do so. Current entry point tc-accepted does not provide any hints where missing T&C's could be signed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBDS-3627) Installer needs to help move past lack of t/c signing
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ]
Denis Golovin edited comment on JBDS-3627 at 8/17/16 1:18 PM:
--------------------------------------------------------------
https://www.redhat.com/wapps/ugc/register.html does not help, I can create a user and then if I try to use it with res service
{code} curl -u user:path https://developers.redhat.com/download-manager/jdf/file/cdk-2.1.0.zip?wor...
it says: "Please, use a valid user name and password!". After I login to developers.redhat.com account and accept T&C's new account works just fine with jdf download manager links and I have no T&C's related problems.
was (Author: dgolovin):
https://www.redhat.com/wapps/ugc/register.html does not help, I can create a user and then if I try to use it with res service it says: "Please, use a valid user name and password!". After I login to developers.redhat.com account and accept T&C's new account works just fine with jdf download manager links and no T&C's related problems.
> Installer needs to help move past lack of t/c signing
> -----------------------------------------------------
>
> Key: JBDS-3627
> URL: https://issues.jboss.org/browse/JBDS-3627
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Reporter: Joshua Wilson
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 10.1.0.AM3
>
> Attachments: Installer-not-signed-tc.PNG
>
>
> DevSuite installer uses "REST services in JBoss Download Manager" explained here https://mojo.redhat.com/docs/DOC-940689.
> DevSuite Intsaller follows the explanation for tc-accepted entry point [code is here|https://github.com/redhat-developer-tooling/developer-platform-insta...]. It uses file from previous CDK release (published in cdn and available through download manager) to do verification:
> 1. that provided credentials are valid;
> 2. that required T&C's are signed.
> There are two major use cases for developers installing DevSuite using Installer:
> 1. Direct download - when developer sign in to developers.redhat.com and download installer himeslf;
> 2. Shared installer - when someone share installer with developers without account.
> There two kind of users involved in those scenarios above:
> 1. New users that must go through registration process;
> 2. Registered users.
> *Direct download*
> For new ones registration process is really simple now. After creating RHD account and downloading installer there is no additional steps to get through installation.
> For already registered users there could be problems related to T&C's and authentication reported here https://issues.jboss.org/browse/RHDENG-579.
> So far there are two kind of problems:
> 1. Users can login and download DevSuite installer, but cannot use the same credentials to install;
> 2. Users that can login in to developers.redhat.com and get request to sign additional T&C's but credentials for the same user in DevSuite Installer reported as invalid when REST tc-accepted entry point is used
> *Shared Download*
> In this scenario new users without account can press Register link, then go through registration process in browser return back to installer and use new account credentials for installation.
> Registered users could need to sign additional T&C's if missing and would be good to show external link to do so. Current entry point tc-accepted does not provide any hints where missing T&C's could be signed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBTIS-834) JBTIS Target Platform - Mars - add swtbot.ide feature dependency for Fuse/SY
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-834?page=com.atlassian.jira.plugin.... ]
Paul Leacu updated JBTIS-834:
-----------------------------
Description:
*Reason:* IS dependency for Fuse/SY
*Project page/sources:*
*Version:* 4.3.3
*License and owner:* EPL
*Original p2 repo:*
*JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/swtbot/2.3.0/
*Include Sources:* Yes
*Affected JBoss Tools components:* Integration Stack
*Include in JBDS:* Yes JBDSIS
*Type of dependency:* testing|central-only|distribution
*List of bundles added/removed:*
{code}
> org.eclipse.swtbot.eclipse.spy [2.3.0.201506081302]
> org.eclipse.swtbot.generator.jdt [2.3.0.201506081302]
> org.eclipse.swtbot.ide.feature.group [2.3.0.201506081302]
> org.eclipse.swtbot.ide.feature.jar [2.3.0.201506081302]
> org.eclipse.swtbot.generator.rules.workbench [2.3.0.201506081302]
> org.eclipse.swtbot.generator [2.3.0.201506081302]
> org.eclipse.swtbot.generator.feature.feature.jar [2.3.0.201506081302]
> org.eclipse.swtbot.generator.ui [2.3.0.201506081302]
> org.eclipse.swtbot.eclipse.ui [2.3.0.201506081302]
> org.eclipse.swtbot.generator.feature.feature.group [2.3.0.201506081302]
=== Summary ===
file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform.target.repo contains 10 unique IUs
{code}
The JBT core TP dependencies are:
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5...
was:
*Reason:* IS dependency for Fuse/SY
*Project page/sources:*
*Version:* 4.3.3
*License and owner:* EPL
*Original p2 repo:*
*JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/swtbot/2.3.0/
*Include Sources:* Yes
*Affected JBoss Tools components:* Integration Stack
*Include in JBDS:* Yes JBDSIS
*Type of dependency:* testing|central-only|distribution
*List of bundles added/removed:*
{code}
{code}
The JBT core TP dependencies are:
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5...
> JBTIS Target Platform - Mars - add swtbot.ide feature dependency for Fuse/SY
> ----------------------------------------------------------------------------
>
> Key: JBTIS-834
> URL: https://issues.jboss.org/browse/JBTIS-834
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.3.2.Final-TP
> Reporter: Paul Leacu
> Assignee: Paul Leacu
>
> *Reason:* IS dependency for Fuse/SY
> *Project page/sources:*
> *Version:* 4.3.3
> *License and owner:* EPL
> *Original p2 repo:*
> *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/swtbot/2.3.0/
> *Include Sources:* Yes
> *Affected JBoss Tools components:* Integration Stack
> *Include in JBDS:* Yes JBDSIS
> *Type of dependency:* testing|central-only|distribution
> *List of bundles added/removed:*
> {code}
> > org.eclipse.swtbot.eclipse.spy [2.3.0.201506081302]
> > org.eclipse.swtbot.generator.jdt [2.3.0.201506081302]
> > org.eclipse.swtbot.ide.feature.group [2.3.0.201506081302]
> > org.eclipse.swtbot.ide.feature.jar [2.3.0.201506081302]
> > org.eclipse.swtbot.generator.rules.workbench [2.3.0.201506081302]
> > org.eclipse.swtbot.generator [2.3.0.201506081302]
> > org.eclipse.swtbot.generator.feature.feature.jar [2.3.0.201506081302]
> > org.eclipse.swtbot.generator.ui [2.3.0.201506081302]
> > org.eclipse.swtbot.eclipse.ui [2.3.0.201506081302]
> > org.eclipse.swtbot.generator.feature.feature.group [2.3.0.201506081302]
> === Summary ===
> file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform.target.repo contains 10 unique IUs
> {code}
> The JBT core TP dependencies are:
> http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (ERT-395) NPE when opening/closing the Properties view [EBZ#499849]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-395:
---------------------------------------
Summary: NPE when opening/closing the Properties view [EBZ#499849]
Key: ERT-395
URL: https://issues.jboss.org/browse/ERT-395
Project: Eclipse Release Train
Issue Type: Task
Components: Linux Tools
Reporter: Friendly Jira Robot
Putting the Docker Explorer and the Properties view side by side, when selecting a docker image in the former, content is shown in the latter. When closing the properties view, I got an NPE:
java.lang.NullPointerException
at org.eclipse.linuxtools.internal.docker.ui.views.BasePropertySection.dispose(BasePropertySection.java:174)
at org.eclipse.ui.views.properties.tabbed.TabContents$2.run(TabContents.java:127)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
at org.eclipse.ui.views.properties.tabbed.TabContents.dispose(TabContents.java:130)
at org.eclipse.ui.views.properties.tabbed.TabbedPropertySheetPage.disposeTabs(TabbedPropertySheetPage.java:624)
at org.eclipse.ui.views.properties.tabbed.TabbedPropertySheetPage.disposeContributor(TabbedPropertySheetPage.java:457)
at org.eclipse.ui.views.properties.tabbed.TabbedPropertySheetPage.dispose(TabbedPropertySheetPage.java:482)
at org.eclipse.ui.views.properties.PropertySheet.doDestroyPage(PropertySheet.java:221)
at org.eclipse.ui.part.PageBookView.removePage(PageBookView.java:864)
at org.eclipse.ui.part.PageBookView.dispose(PageBookView.java:509)
at org.eclipse.ui.views.properties.PropertySheet.dispose(PropertySheet.java:186)
at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.invalidate(CompatibilityPart.java:238)
at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.destroy(CompatibilityPart.java:394)
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:498)
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54)
at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:966)
at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:931)
at org.eclipse.e4.core.internal.di.InjectorImpl.uninject(InjectorImpl.java:212)
at org.eclipse.e4.core.internal.di.Requestor.uninject(Requestor.java:170)
at org.eclipse.e4.core.internal.contexts.ContextObjectSupplier$ContextInjectionListener.update(ContextObjectSupplier.java:84)
at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(TrackableComputationExt.java:111)
at org.eclipse.e4.core.internal.contexts.EclipseContext.removeListenersTo(EclipseContext.java:470)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.uninject(ContextInjectionFactory.java:144)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeRemoveGui(PartRenderingEngine.java:927)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$1(PartRenderingEngine.java:846)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$3.run(PartRenderingEngine.java:841)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.removeGui(PartRenderingEngine.java:825)
at org.eclipse.e4.ui.workbench.renderers.swt.ElementReferenceRenderer.disposeWidget(ElementReferenceRenderer.java:112)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeRemoveGui(PartRenderingEngine.java:918)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$1(PartRenderingEngine.java:846)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$3.run(PartRenderingEngine.java:841)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.removeGui(PartRenderingEngine.java:825)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.subscribeTopicToBeRendered(PartRenderingEngine.java:173)
at sun.reflect.GeneratedMethodAccessor148.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54)
at org.eclipse.e4.core.di.internal.extensions.EventObjectSupplier$DIEventHandler.handleEvent(EventObjectSupplier.java:80)
at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:201)
at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197)
at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135)
at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78)
at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39)
at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:94)
at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:60)
at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374)
at org.eclipse.e4.ui.model.application.ui.impl.UIElementImpl.setToBeRendered(UIElementImpl.java:303)
at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.hidePart(PartServiceImpl.java:1350)
at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.hidePart(PartServiceImpl.java:1284)
at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer.closePart(StackRenderer.java:1289)
at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer.access$2(StackRenderer.java:1271)
at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer$7.close(StackRenderer.java:1156)
at org.eclipse.swt.custom.CTabFolder.onMouse(CTabFolder.java:1930)
at org.eclipse.swt.custom.CTabFolder$1.handleEvent(CTabFolder.java:338)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4248)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1501)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1524)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1509)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1313)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698)
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 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)
If I reopen the Properties view, I get a similar error:
java.lang.NullPointerException
at org.eclipse.linuxtools.internal.docker.ui.views.BasePropertySection.dispose(BasePropertySection.java:174)
at org.eclipse.ui.views.properties.tabbed.TabContents$2.run(TabContents.java:127)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
at org.eclipse.ui.views.properties.tabbed.TabContents.dispose(TabContents.java:130)
at org.eclipse.ui.views.properties.tabbed.TabbedPropertySheetPage.disposeTabs(TabbedPropertySheetPage.java:624)
at org.eclipse.ui.views.properties.tabbed.TabbedPropertySheetPage.updateTabs(TabbedPropertySheetPage.java:681)
at org.eclipse.ui.views.properties.tabbed.TabbedPropertySheetPage.setInput(TabbedPropertySheetPage.java:735)
at org.eclipse.ui.views.properties.tabbed.TabbedPropertySheetPage.selectionChanged(TabbedPropertySheetPage.java:555)
at org.eclipse.ui.views.properties.PropertySheet.selectionChanged(PropertySheet.java:405)
at org.eclipse.ui.internal.e4.compatibility.SelectionService.notifyListeners(SelectionService.java:259)
at org.eclipse.ui.internal.e4.compatibility.SelectionService.handlePostSelectionChanged(SelectionService.java:133)
at org.eclipse.ui.internal.e4.compatibility.SelectionService.access$1(SelectionService.java:123)
at org.eclipse.ui.internal.e4.compatibility.SelectionService$3.selectionChanged(SelectionService.java:81)
at org.eclipse.e4.ui.internal.workbench.SelectionAggregator$4.run(SelectionAggregator.java:166)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.e4.ui.internal.workbench.SelectionAggregator.notifyPostListeners(SelectionAggregator.java:163)
at org.eclipse.e4.ui.internal.workbench.SelectionAggregator.access$8(SelectionAggregator.java:161)
at org.eclipse.e4.ui.internal.workbench.SelectionAggregator$8$1.run(SelectionAggregator.java:271)
at org.eclipse.e4.core.contexts.RunAndTrack.runExternalCode(RunAndTrack.java:56)
at org.eclipse.e4.ui.internal.workbench.SelectionAggregator$8.changed(SelectionAggregator.java:268)
at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(TrackableComputationExt.java:114)
at org.eclipse.e4.core.internal.contexts.EclipseContext.processScheduled(EclipseContext.java:343)
at org.eclipse.e4.core.internal.contexts.EclipseContext.set(EclipseContext.java:358)
at org.eclipse.e4.ui.internal.workbench.SelectionServiceImpl.setPostSelection(SelectionServiceImpl.java:36)
at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart$3.selectionChanged(CompatibilityPart.java:132)
at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:878)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:875)
at org.eclipse.jface.viewers.StructuredViewer.handlePostSelect(StructuredViewer.java:1244)
at org.eclipse.ui.navigator.CommonViewer.handlePostSelect(CommonViewer.java:457)
at org.eclipse.jface.viewers.StructuredViewer$5.widgetSelected(StructuredViewer.java:1270)
at org.eclipse.jface.util.OpenStrategy.firePostSelectionEvent(OpenStrategy.java:265)
at org.eclipse.jface.util.OpenStrategy.access$5(OpenStrategy.java:259)
at org.eclipse.jface.util.OpenStrategy$1.lambda$1(OpenStrategy.java:431)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3700)
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 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)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (ERT-396) Connection is not added(same parameters, different name) [EBZ#499854]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-396:
---------------------------------------
Summary: Connection is not added(same parameters, different name) [EBZ#499854]
Key: ERT-396
URL: https://issues.jboss.org/browse/ERT-396
Project: Eclipse Release Train
Issue Type: Task
Components: Linux Tools
Reporter: Friendly Jira Robot
Steps to reproduce:
1. Create connection in Docker Explorer
2. Create connection in Docker Explorer with same parameters as in step 1, but different name.
The second connection is not added.
Docker tooling version:
2.1.0201608170955
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22741) JMX connection to remote server does not work (fs operations, no runtime)
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22741?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-22741:
--------------------------------
Summary: JMX connection to remote server does not work (fs operations, no runtime) (was: JMX connection to remote server does not work (fs operations))
> JMX connection to remote server does not work (fs operations, no runtime)
> -------------------------------------------------------------------------
>
> Key: JBIDE-22741
> URL: https://issues.jboss.org/browse/JBIDE-22741
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 4.4.1.AM2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.4.1.Final
>
>
> I wanted to replicate JBIDE-17181 today. And I cannot replicate that problem.
> But I noticed that jmx connection to a remote wf 8.2 with fs operations doesn't seem to work. I thought there was a long standing issue open for this already, but it turns out this other JIRA is for management mode: JBIDE-20108
> So it seems that neither works right now.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23017) use sshfs to speed up publishing process
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-23017:
----------------------------------
Summary: use sshfs to speed up publishing process
Key: JBIDE-23017
URL: https://issues.jboss.org/browse/JBIDE-23017
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: build
Affects Versions: 4.4.1.AM3
Reporter: Nick Boldt
Currently, publishing from /snapshots to /staging and from /staging to /development requires that we fetch several GBs of data from filemgmt.jboss.org to a temp folder, then push those bits to a new folder on filemgmt.jboss.org.
If we could simply copy bits over sshfs, the process might be a lot faster than these times:
{code}
JBT coretests 1.1G: 59m20
JBT core 1.2G: 64m23
devstudio (copy from filemgmt to filemgmt) 2.4G: 2h13
devstudio (copy from local to www.qa) 3.1G: 6mins(?)
{code}
To make this work, however, we need more slaves to have sshfs installed. Currently, it appears that only dev01 [1] is so equipped. And that slave, currently, has a build queue more than 170 jobs long, making it impractical to even TEST publishing over sshfs.
[1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev01-rhel5-x86/
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22657) smart import nullpointer
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22657?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22657:
-------------------------------
Fix Version/s: 4.4.1.Final
(was: 4.4.1.AM3)
> smart import nullpointer
> ------------------------
>
> Key: JBIDE-22657
> URL: https://issues.jboss.org/browse/JBIDE-22657
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Fix For: 4.4.1.Final, 4.5.0.AM1
>
>
> when using smartimport to import https://github.com/maxandersen/imapfilter-docker.git from disk I got a NPE in jaxrs:
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.ws.jaxrs.ui.internal.importer.JaxRsConfigurator.canConfigure(JaxRsConfigurator.java:66)
> at org.eclipse.ui.internal.wizards.datatransfer.SmartImportJob.importProjectAndChildrenRecursively(SmartImportJob.java:466)
> at org.eclipse.ui.internal.wizards.datatransfer.SmartImportJob.run(SmartImportJob.java:242)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months