September 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23178) cdk tools not reading / closing process streams correctly

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-23178: ----------------------------------- Summary: cdk tools not reading / closing process streams correctly Key: JBIDE-23178 URL: https://issues.jboss.org/browse/JBIDE-23178 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdk Affects Versions: 4.4.1.Final Reporter: Rob Stryker Calls to environment manager or vagrant status often fail with a timeout. Sometimes they can be worked around, so the user never sees the error. However the implementation is incorrect. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23166) MBean Stubs New Wizard cannot be open

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23166?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23166: -------------------------------- Fix Version/s: 4.4.2.AM1 > MBean Stubs New Wizard cannot be open > ------------------------------------- > > Key: JBIDE-23166 > URL: https://issues.jboss.org/browse/JBIDE-23166 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.1.Final > Reporter: Denis Golovin > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.4.2.AM1 > > Attachments: mbinstubs.gif > > > It just throws exception below > {code}The selected wizard could not be started. > Plug-in org.jboss.ide.eclipse.as.ui.mbeans was unable to load class org.jboss.ide.eclipse.as.ui.mbeans.wizards.NewMBeanWizard. > org.jboss.ide.eclipse.as.ui.mbeans.wizards.NewMBeanWizard cannot be found by org.jboss.ide.eclipse.as.ui.mbeans_3.2.1.v20160607-2122{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23177) Server Editor: Combo items have wrong size

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23177?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-23177: --------------------------------------- The patch from JBIDE-22912 fixes this issue, too. > Server Editor: Combo items have wrong size > ------------------------------------------ > > Key: JBIDE-23177 > URL: https://issues.jboss.org/browse/JBIDE-23177 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM1 > Reporter: Marián Labuda > Labels: openshift_v3, server_editor > Attachments: combos.png > > > When I open an OpenShift 3 Server Editor the combo boxes have weird size, there are overlapping widgets. > !combos.png! > Spotted on Fedora 24 with GTK 3. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4050) CDK 2.2 installation failed in devsuite 1.1.0-GA-20160915

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4050?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-4050: ------------------------------------- Your original question was related to different error though: {code}Fri, 16 Sep 2016 05:51:09 GMT-ERROR: cdk - Error: Command failed: vagrant box add --name cdkv2 rhel-vagrant-virtualbox.box Unable to load the EventMachine C extension; To use the pure-ruby reactor, require 'em/pure_ruby' Vagrant failed to initialize at a very early stage:{code} This error was fixed probably by removing ruby and ruby related folders in your PROFILE. I suspect if you were active user of ruby and had previous versions of ruby installed you might get into this problem because of another upstream issue here https://github.com/eventmachine/eventmachine/issues/536 related to pre-compiled versions of ruby gems can be incompatible. > CDK 2.2 installation failed in devsuite 1.1.0-GA-20160915 > --------------------------------------------------------- > > Key: JBDS-4050 > URL: https://issues.jboss.org/browse/JBDS-4050 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.GA > Environment: **Operating System** > Windows 10 Pro 64 Bit > **Devsuite version** > Devsuite 1.1.0-GA-20160915-140 > Reporter: Budh Ram Gurung > Assignee: Denis Golovin > Fix For: 10.2.0.AM1 > > Attachments: 1.devsuite.PNG, 2.c++.PNG, 3.vagrant_cli.PNG, install-iteration1.log, install.log, vagrant-up-debug-log.txt > > > After passing through registration, on clicking 'Install' button in the installer window, the CDK 2.2 get failed message. > Check the attached screenshots. > I also tried to add vagrant box through cygwin shell but getting some `eventmachine.so` related error. > *NOTE*: I am able to successfully add the cdk box on Vagrant 1.7.4 version. > Other information, I had following things pre-installed before running the installer: > - Docker toolbox (probably it remain there when I was trying it last time) > - Vagrant 1.8.1 > - Cygwin > - VirtualBox 5.0.26 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4050) CDK 2.2 installation failed in devsuite 1.1.0-GA-20160915

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4050?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-4050: ------------------------------------- Surprisingly, while I was writing previous answer, I found the reason of curl error in your log, screenshot was a big help here :) You installed C++ re-distributional package for 64-bit platform, which is logical, because you have 64-bit system. But in this case you have to install 32-bit package, because vagrant provides curl, bsdtar and zip as part of mingw for 32-bit windows. Upstream error can be seen here https://github.com/mitchellh/vagrant/issues/6852. > CDK 2.2 installation failed in devsuite 1.1.0-GA-20160915 > --------------------------------------------------------- > > Key: JBDS-4050 > URL: https://issues.jboss.org/browse/JBDS-4050 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.GA > Environment: **Operating System** > Windows 10 Pro 64 Bit > **Devsuite version** > Devsuite 1.1.0-GA-20160915-140 > Reporter: Budh Ram Gurung > Assignee: Denis Golovin > Fix For: 10.2.0.AM1 > > Attachments: 1.devsuite.PNG, 2.c++.PNG, 3.vagrant_cli.PNG, install-iteration1.log, install.log, vagrant-up-debug-log.txt > > > After passing through registration, on clicking 'Install' button in the installer window, the CDK 2.2 get failed message. > Check the attached screenshots. > I also tried to add vagrant box through cygwin shell but getting some `eventmachine.so` related error. > *NOTE*: I am able to successfully add the cdk box on Vagrant 1.7.4 version. > Other information, I had following things pre-installed before running the installer: > - Docker toolbox (probably it remain there when I was trying it last time) > - Vagrant 1.8.1 > - Cygwin > - VirtualBox 5.0.26 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4050) CDK 2.2 installation failed in devsuite 1.1.0-GA-20160915

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4050?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-4050: ------------------------------------- Cygwin required only because of openssh and rsync packages. curl, zip and bsdtar are coming with vagrant itself > CDK 2.2 installation failed in devsuite 1.1.0-GA-20160915 > --------------------------------------------------------- > > Key: JBDS-4050 > URL: https://issues.jboss.org/browse/JBDS-4050 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.GA > Environment: **Operating System** > Windows 10 Pro 64 Bit > **Devsuite version** > Devsuite 1.1.0-GA-20160915-140 > Reporter: Budh Ram Gurung > Assignee: Denis Golovin > Fix For: 10.2.0.AM1 > > Attachments: 1.devsuite.PNG, 2.c++.PNG, 3.vagrant_cli.PNG, install-iteration1.log, install.log, vagrant-up-debug-log.txt > > > After passing through registration, on clicking 'Install' button in the installer window, the CDK 2.2 get failed message. > Check the attached screenshots. > I also tried to add vagrant box through cygwin shell but getting some `eventmachine.so` related error. > *NOTE*: I am able to successfully add the cdk box on Vagrant 1.7.4 version. > Other information, I had following things pre-installed before running the installer: > - Docker toolbox (probably it remain there when I was trying it last time) > - Vagrant 1.8.1 > - Cygwin > - VirtualBox 5.0.26 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4050) CDK 2.2 installation failed in devsuite 1.1.0-GA-20160915

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4050?page=com.atlassian.jira.plugin.... ] Denis Golovin edited comment on JBDS-4050 at 9/16/16 4:13 PM: -------------------------------------------------------------- Cygwin required only because of openssh and rsync packages. curl, zip and bsdtar are coming with vagrant itself. was (Author: dgolovin): Cygwin required only because of openssh and rsync packages. curl, zip and bsdtar are coming with vagrant itself > CDK 2.2 installation failed in devsuite 1.1.0-GA-20160915 > --------------------------------------------------------- > > Key: JBDS-4050 > URL: https://issues.jboss.org/browse/JBDS-4050 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.GA > Environment: **Operating System** > Windows 10 Pro 64 Bit > **Devsuite version** > Devsuite 1.1.0-GA-20160915-140 > Reporter: Budh Ram Gurung > Assignee: Denis Golovin > Fix For: 10.2.0.AM1 > > Attachments: 1.devsuite.PNG, 2.c++.PNG, 3.vagrant_cli.PNG, install-iteration1.log, install.log, vagrant-up-debug-log.txt > > > After passing through registration, on clicking 'Install' button in the installer window, the CDK 2.2 get failed message. > Check the attached screenshots. > I also tried to add vagrant box through cygwin shell but getting some `eventmachine.so` related error. > *NOTE*: I am able to successfully add the cdk box on Vagrant 1.7.4 version. > Other information, I had following things pre-installed before running the installer: > - Docker toolbox (probably it remain there when I was trying it last time) > - Vagrant 1.8.1 > - Cygwin > - VirtualBox 5.0.26 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23177) Server Editor: Combo items have wrong size

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23177?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-23177: --------------------------------------- I would not mark it as a duplicate of JBIDE-22912, bcs. Pull request applying in JBIDE-22912 is fixing Deploy docker image wizard and thus if we mark this as duplicate, it wont get fixed, because this is Server Editor (double click on OpenShift 3 Server Adapter). I linked JBIDE-22912 as related and the fix will be, I think, the same. > Server Editor: Combo items have wrong size > ------------------------------------------ > > Key: JBIDE-23177 > URL: https://issues.jboss.org/browse/JBIDE-23177 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM1 > Reporter: Marián Labuda > Labels: openshift_v3, server_editor > Attachments: combos.png > > > When I open an OpenShift 3 Server Editor the combo boxes have weird size, there are overlapping widgets. > !combos.png! > Spotted on Fedora 24 with GTK 3. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-22362: ------------------------------------- [~adietish] I'm planning to drag this issue to the next in order to finally figure out how to tackle it. Do you happen to try my change ^ ? > Server Adapter: Static changes done to nodejs application are not visible > ------------------------------------------------------------------------- > > Key: JBIDE-22362 > URL: https://issues.jboss.org/browse/JBIDE-22362 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Ilya Buziuk > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.2.AM1 > > > I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating. > So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ] Ilya Buziuk edited comment on JBIDE-22362 at 9/16/16 1:07 PM: -------------------------------------------------------------- [~adietish] I'm planning to drag this issue to the next sprint in order to finally figure out how to tackle it. Do you happen to try my change ^ ? was (Author: ibuziuk): [~adietish] I'm planning to drag this issue to the next in order to finally figure out how to tackle it. Do you happen to try my change ^ ? > Server Adapter: Static changes done to nodejs application are not visible > ------------------------------------------------------------------------- > > Key: JBIDE-22362 > URL: https://issues.jboss.org/browse/JBIDE-22362 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Ilya Buziuk > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.2.AM1 > > > I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating. > So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 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 September 2016