September 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23039) Need an interactive terminal that fits specific requirements

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23039?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-23039: --------------------------------------- For Rob: These are the plugins I used on Windows where I have the problem with input in Terminal: {code} $ vagrant plugin list vagrant-registration (1.3.0) - Version Constraint: 1.3.0 vagrant-service-manager (1.3.3) - Version Constraint: 1.3.3 vagrant-share (1.1.5, system) vagrant-sshfs (1.2.0) - Version Constraint: 1.2.0 {code} {code} $ vagrant -v Vagrant 1.8.1 {code} Vagrant box: rhel-cdk-kubernetes-7.2-28.x86_64.vagrant-virtualbox.box > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23016) When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23016?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-23016: --------------------------------------- OK, so this is what happens on Windows 10: When I start cdk 2.2 rc3 (no landrush) in CLI as an admin, I am shown the Windows full-screen prompt for admin permissions twice because VirtualBox needs to set up an interface and something else. But as an admin user running this, I don't need to enter credentials, I just have to confirm this action. When I start cdk 2.2 rc1 (landrush included) in CLI as a normal user, I am shown the Windows full-screen prompt for admin credentials (where I need to log in as an admin) 4 times - twice for virtualbox and twice for landrush. Next, I did vagrant destroy and vagrant up and I was asked for permissions only once - a Ruby process. This was one of the two needed by landrush in the previous vagrant up. So that's good - that's enough for my Eclipse test. Now onto the finale: I set up this cdk in devstudio 10.1.0.GA and launched it. And, as expected, during vagrant up, Windows showed the full-screen prompt for admin credentials for this Ruby process - same as from CLI. So the conclusion is that this is a non-problem on Windows and we don't need anything special to handle this use case there - we don't need to be able to enter input into the console/terminal in Eclipse on Windows. Side note: Every vagrant command I do (like vagrant up or vagrant destroy) with landrush installed starts with this output: The system cannot find the path specified. I don't have a clue what that is. > When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-23016 > URL: https://issues.jboss.org/browse/JBIDE-23016 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.1.AM3 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.2.AM1 > > > The problem is that the first time you do vagrant up with cdk that has landrush set up, you will be asked to provide your sudo password so that landrush can be set up (unless you used it elsewhere already). > This is definitely true on Mac, most likely on Linux also. On Windows, I expect that you will probably just be shown the system prompt for agreeing that the process uses admin rights. > When I did this yesterday (while testing cdk 2.2 rc1), I actually started it from terminal first, so I could enter my password in the console. But I'm pretty sure this wouldn't work in Eclipse. So we need to figure out how to handle this scenario and also test what happens on Windows after installing devsuite and then starting cdk from devstudio - that is our most important use case. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4048) Checking of installed OpenJDK gets stucked on windows 7

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBDS-4048?page=com.atlassian.jira.plugin.... ] Ondrej Dockal commented on JBDS-4048: ------------------------------------- Downloading and installing of components with the fix ends up correctly. Although, msiexec process is still running, installer finishes installation. > Checking of installed OpenJDK gets stucked on windows 7 > ------------------------------------------------------- > > Key: JBDS-4048 > URL: https://issues.jboss.org/browse/JBDS-4048 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.GA > Environment: Windows 7, x86_64 > Reporter: Ondrej Dockal > Assignee: Denis Golovin > Priority: Blocker > Fix For: 10.1.0.GA > > Attachments: InstallerStucked.png > > > Checking of installed component gets stucked. See pic. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23127) blog about the improvements jboss tools team did to Neon

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23127?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-23127: ---------------------------------------- [~lincolnthree] Can you please point me to the procedure to prepare and publish a blog post on developers.redhat.com ? > blog about the improvements jboss tools team did to Neon > -------------------------------------------------------- > > Key: JBIDE-23127 > URL: https://issues.jboss.org/browse/JBIDE-23127 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > > Neon is out and we did a lot of great stuff in the platform > around smart import, auto download of extensions, zoom, etc. > I thought it would be great to do a blog posting about this work > on tools.jboss.org for the Eclipse Neon release > Audience: users of Eclipse and making internal and external to Red Hat aware of the improvements made. > The target would be http://developers.redhat.com/blog -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23131) Integration tests: move openshift integration tests to jbosstools/openshift repo

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23131?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23131: ------------------------------------- Original Estimate: 1 day Remaining Estimate: 1 day > Integration tests: move openshift integration tests to jbosstools/openshift repo > -------------------------------------------------------------------------------- > > Key: JBIDE-23131 > URL: https://issues.jboss.org/browse/JBIDE-23131 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: integration-test > Fix For: 4.4.2.AM1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > we need to move jbosstools/openshift integration tests from their [repo|https://github.com/jbosstools/jbosstools-integration-tests] to the jbosstools/openshift tools [repo|https://github.com/jbosstools/jbosstools-openshift] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23131) Integration tests: move openshift integration tests to jbosstools/openshift repo

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23131?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23131: ------------------------------------- Story Points: 8 > Integration tests: move openshift integration tests to jbosstools/openshift repo > -------------------------------------------------------------------------------- > > Key: JBIDE-23131 > URL: https://issues.jboss.org/browse/JBIDE-23131 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: integration-test > Fix For: 4.4.2.AM1 > > > we need to move jbosstools/openshift integration tests from their [repo|https://github.com/jbosstools/jbosstools-integration-tests] to the jbosstools/openshift tools [repo|https://github.com/jbosstools/jbosstools-openshift] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23131) Integration tests: move openshift integration tests to jbosstools/openshift repo

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23131?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23131: ------------------------------------------ The only problem I currently see - if integration-tests are moved to the components - is that we need an approach to keep the current ability to run all integration-tests across all components (something that is fairly easy right now given integration-tests are now all in 1 repo: jbosstools-integration-tests). A possible solution is to provide a profile "integration-tests" in all components (that configures shurefire to include integration-tests). All integration-tests could then be run when checking out a jbosstools-all repo that has git-submodules to the component repos by running a build with the "integration-tests" profile. The drawback of this is a much longer runtime for integration-tests since it involves building jbosstools-all (vs jbosstools-integration-tests only). [~mlabuda][~jeffmaury][~bdshadow][~akazakov] Thoughts? > Integration tests: move openshift integration tests to jbosstools/openshift repo > -------------------------------------------------------------------------------- > > Key: JBIDE-23131 > URL: https://issues.jboss.org/browse/JBIDE-23131 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: integration-test > Fix For: 4.4.2.AM1 > > > we need to move jbosstools/openshift integration tests from their [repo|https://github.com/jbosstools/jbosstools-integration-tests] to the jbosstools/openshift tools [repo|https://github.com/jbosstools/jbosstools-openshift] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23144) Integration with Keycloak

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23144?page=com.atlassian.jira.plugi... ] Gorkem Ercan closed JBIDE-23144. -------------------------------- Resolution: Migrated to another ITS > Integration with Keycloak > ------------------------- > > Key: JBIDE-23144 > URL: https://issues.jboss.org/browse/JBIDE-23144 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Gorkem Ercan > > Che should be able to authenticate/authorize through keycloak. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23144) Integration with Keycloak

by Gorkem Ercan (JIRA)

Gorkem Ercan created JBIDE-23144: ------------------------------------ Summary: Integration with Keycloak Key: JBIDE-23144 URL: https://issues.jboss.org/browse/JBIDE-23144 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: server Reporter: Gorkem Ercan Che should be able to authenticate/authorize through keycloak. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4048) Checking of installed OpenJDK gets stucked on windows 7

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBDS-4048?page=com.atlassian.jira.plugin.... ] Ondrej Dockal commented on JBDS-4048: ------------------------------------- [~dgolovin] At the time I was checking the functionality of the fix I was just debugging installer via npm start, thus, I was not able to continue to download/install. Nevertheless, I am bundling the installer with fix right now, give me a while to report results. > Checking of installed OpenJDK gets stucked on windows 7 > ------------------------------------------------------- > > Key: JBDS-4048 > URL: https://issues.jboss.org/browse/JBDS-4048 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.GA > Environment: Windows 7, x86_64 > Reporter: Ondrej Dockal > Assignee: Denis Golovin > Priority: Blocker > Fix For: 10.1.0.GA > > Attachments: InstallerStucked.png > > > Checking of installed component gets stucked. See pic. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 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