September 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23181) Remove unused imports in org.jboss.tools.hibernate.jpt.core.internal.context.HibernateIdMapping

by Koen Aers (JIRA)

Koen Aers created JBIDE-23181: --------------------------------- Summary: Remove unused imports in org.jboss.tools.hibernate.jpt.core.internal.context.HibernateIdMapping Key: JBIDE-23181 URL: https://issues.jboss.org/browse/JBIDE-23181 Project: Tools (JBoss Tools) Issue Type: Task Components: hibernate Affects Versions: 4.4.1.Final Reporter: Koen Aers -- 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 Budh Ram Gurung (JIRA)

[ https://issues.jboss.org/browse/JBDS-4050?page=com.atlassian.jira.plugin.... ] Budh Ram Gurung resolved JBDS-4050. ----------------------------------- Resolution: Done Resolving this issue as now I am able to install CDK through devsuite properly. Please check the comments for more details. > 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 Budh Ram Gurung (JIRA)

[ https://issues.jboss.org/browse/JBDS-4050?page=com.atlassian.jira.plugin.... ] Budh Ram Gurung commented on JBDS-4050: --------------------------------------- [~dgolovin] Hi Denis, I am now able to properly install devsuite. The only problem I had was I didn't had the "C++ re-distribution package x86 version of 2010". *Note:* Even with "C++ redistribution package x86 2015" didn't work. Probably, good to note down for troubleshooting purpose. > 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-23039) Need an interactive terminal that fits specific requirements

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23039?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-23039: ------------------------------------- Hi Hardy: We were definitely setting the vagrant_detected_os environment variable every time. It was always there. The problem was that if we didn't also pass a SUB_USERNAME and SUB_PASSWORD, the registration plugin would try to prompt us to enter them... and vagrant as a whole has no way to prompt users without using a TTY solution. The error is thrown from vagrant / ruby directly, and it's because the registration plugin asked them to prompt us and they had no way to do it. The solution that I've found now is to use some code in eclipse cdt (c++ dev tools) which can create a PTY (pseudo-tty) to wrap every command we run in windows. There is a downside to it though: it adds color codes to EVERY command run (even a simple java TestClass). Yes, I know VAGRANT_NO_COLOR is a valid environment variable ;) The problem is the PTY lib is adding the color codes, not vagrant. So My new patch (https://github.com/jbosstools/jbosstools-openshift/pull/1312) makes sure to only use the cdt pty solution when we're presenting stuff to the user in a terminal, but for our calls to vagrant status or vagrant service-manager, we use the old Runtime.getRuntime().exec(etc). THis still has the very small potential to fail if in the future we ever make vagrant status or vagrant service-manager prompt the user or use tty functionality... but that is extremely unlikely. So I think the newest patch is the best and it seems to work in all cases (with a small UI problem in mac, but, I mean, mac's weird). > Need an interactive terminal that fits specific requirements > ------------------------------------------------------------ > > Key: JBIDE-23039 > URL: https://issues.jboss.org/browse/JBIDE-23039 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.4.1.AM2 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.2.AM1 > > Attachments: vagranttty.png > > > CDK Tools requires a terminal that allows interactivity of i/o. The full set of requirements is a bit difficult to find a solution for. > 1) I must be able to get a Process or IProcess object when a command is run > 2) I must be able to get an event or know when the process terminates > 3) The terminal or console must be interactive and allow user input when prompted. > 4) It must behave as in 3) for 'vagrant' commands and any and all associated plugins. > These three requirements thus far seem impossible to solve. Solutions that have been attempted are: > 1) Creating a java Process by myself via Runtime.exec. The interactive prompts never arrive and there is no API for Process to know when it is waiting for input. > 2) Using the external-tools launch configuration. When running a command like mvn, the console that pops up seems to allow input from the user, and functions as expected. However, when running a command such as vagrant, such prompts are not provided. In our usecase, the following behavior is observed: > a) During vagrant-registration prompts, the console indicates it is not a TTY terminal and cannot allow input > b) During a landrush prompt for superuser status, no prompt is made, no TTY message is listed, and the process appears to have frozen > 3) Launching / Opening a tm.terminal view. This solution fails requirements 1 and 2. We are not able to get a Process or an IProcess when a command is launched in a proper interactive terminal. This means we can have no way to know when the process has completed. > Other options have been explored but ended up at dead ends and not worth mentioning. The real question is why interactive behavior is visible when using external-tools launch config for maven, but is not visible when running vagrant. > Is this a function of the way the vagrant commands display or prompt for input? Why does vagrant-registration require a TTY terminal, but maven does not? Is this something that can be fixed upstream? > No other obvious solutions have presented themselves in the past year. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23180) CDKLaunchController (and others) calling ui-blocking getPassword() even when user not passing credentials

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23180?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-23180. --------------------------------- Fix Version/s: 4.4.2.AM1 Assignee: Rob Stryker Resolution: Done Fixed at https://github.com/jbosstools/jbosstools-openshift/pull/1315 > CDKLaunchController (and others) calling ui-blocking getPassword() even when user not passing credentials > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23180 > URL: https://issues.jboss.org/browse/JBIDE-23180 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.2.AM1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.2.AM1 > > > Even when a user has unchecked the option to pass credentials to vagrant via environment variables, the user is still being prompted for a username and password. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23180) CDKLaunchController (and others) calling ui-blocking getPassword() even when user not passing credentials

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-23180: ----------------------------------- Summary: CDKLaunchController (and others) calling ui-blocking getPassword() even when user not passing credentials Key: JBIDE-23180 URL: https://issues.jboss.org/browse/JBIDE-23180 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdk Affects Versions: 4.4.2.AM1 Reporter: Rob Stryker Even when a user has unchecked the option to pass credentials to vagrant via environment variables, the user is still being prompted for a username and password. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

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

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23178?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-23178. --------------------------------- Fix Version/s: 4.4.2.AM1 Assignee: Rob Stryker Resolution: Done change pushed to master https://github.com/jbosstools/jbosstools-openshift/pull/1314 > 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 > Assignee: Rob Stryker > Fix For: 4.4.2.AM1 > > > 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-23178) cdk tools not reading / closing process streams correctly

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23178?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-23178: ------------------------------------- To be clear what was happening here: Old code was launching the process, and then waiting for the process to terminate before reading the streams. This was incorrect behavior. Once the stream's buffer filled up, the process cannot die until it can finish its output. Meanwhile my code was refusing to read the streams until the process died. Logic was very backwards. It should be fixed with PR https://github.com/jbosstools/jbosstools-openshift/pull/1314 > 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-23179) "poweroff" not recognized as a vagrant state in master

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23179?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-23179. --------------------------------- Fix Version/s: 4.4.2.AM1 Assignee: Rob Stryker Resolution: Done pushed to master https://github.com/jbosstools/jbosstools-openshift/pull/1313 > "poweroff" not recognized as a vagrant state in master > ------------------------------------------------------ > > Key: JBIDE-23179 > URL: https://issues.jboss.org/browse/JBIDE-23179 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.2.AM1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.2.AM1 > > > A vagrant machine in state not_created is not recognized at all. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23179) "poweroff" not recognized as a vagrant state in master

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-23179: ----------------------------------- Summary: "poweroff" not recognized as a vagrant state in master Key: JBIDE-23179 URL: https://issues.jboss.org/browse/JBIDE-23179 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdk Affects Versions: 4.4.2.AM1 Reporter: Rob Stryker A vagrant machine in state not_created is not recognized at all. -- 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