August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23065) test failure in org.jboss.tools.jsf.vpe.jsf.test

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23065?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-23065: ------------------------------------- PR was sent - https://github.com/jbosstools/jbosstools-javaee/pull/413 All OpenOn tests were removed / failing ajax4jsf & facelets tests were disabled. > test failure in org.jboss.tools.jsf.vpe.jsf.test > ------------------------------------------------- > > Key: JBIDE-23065 > URL: https://issues.jboss.org/browse/JBIDE-23065 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-templates > Affects Versions: 4.4.1.AM3 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.4.1.Final > > > Need to remove the following tests - http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > Those tests are also failing locally -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4032) [cdk installer] weird errors during startup

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-4032?page=com.atlassian.jira.plugin.... ] Rob Stryker commented on JBDS-4032: ----------------------------------- Newest log after uninstall / re-install attempt: {code} ==> 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: Configuring and enabling network interfaces... ==> default: Landrush IP not installed in guest yet (or it's an outdated version). Installing now. ==> default: Copying TLS certificates to C:/DevelopmentSuite6/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker ==> default: Rsyncing folder: /cygdrive/c/DevelopmentSuite6/cdk/components/rhel/rhel-ose/ => /vagrant There was an error when attempting to rsync a synced folder. Please inspect the error message below for more info. Host path: /cygdrive/c/DevelopmentSuite6/cdk/components/rhel/rhel-ose/ Guest path: /vagrant Command: rsync --verbose --archive --delete -z --copy-links --chmod=ugo=rwX --no-perms --no-owner --no-group --rsync-path sudo rsync -e ssh -p 2222 -o ControlMaster=auto -o ControlPath=C:/Users/Administrator/AppData/Local/Temp/ssh.549 -o ControlPersist=10m -o StrictHostKeyChecking=no -o IdentitiesOnly=true -o UserKnownHostsFile=/dev/null -i 'C:/DevelopmentSuite6/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/private_key' --exclude .vagrant/ /cygdrive/c/DevelopmentSuite6/cdk/components/rhel/rhel-ose/ vagrant@127.0.0.1:/vagrant Error: Warning: Permanently added '[127.0.0.1]:2222' (ECDSA) to the list of known hosts. mm_receive_fd: no message header process_mux_new_session: failed to receive fd 0 from slave mm_send_fd: sendmsg(2): Broken pipe mux_client_request_session: send fds failed rsync: connection unexpectedly closed (0 bytes received so far) [sender] rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.1] {code} > [cdk installer] weird errors during startup > ------------------------------------------- > > Key: JBDS-4032 > URL: https://issues.jboss.org/browse/JBDS-4032 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Reporter: Rob Stryker > > After a previously-working environment, I installed build http://cdk-builds.usersys.redhat.com/builds/nightly/devsuite/2016-08-24_0... > Once I did that, I get teh following environment: > Administrator@LBDZ-20120704HU MINGW64 /c/DevelopmentSuite4/cdk/components/rhel/rhel-ose > $ vagrant -v > Vagrant 1.8.1 > Administrator@LBDZ-20120704HU MINGW64 /c/DevelopmentSuite4/cdk/components/rhel/rhel-ose > $ vagrant plugin list > landrush (1.1.2) > vagrant-registration (1.2.2) > - Version Constraint: 1.2.2 > vagrant-service-manager (1.1.0) > - Version Constraint: 1.1.0 > vagrant-share (1.1.5, system) > vagrant-sshfs (1.1.0) > - Version Constraint: 1.1.0 > Vagrant up had following log: https://paste.fedoraproject.org/418594/77989147/ > That log indicated I should read another log. The 2nd log is: https://paste.fedoraproject.org/418595/26780201/ > Removing the box and re-adding it did not seem to help. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23065) test failure in org.jboss.tools.jsf.vpe.jsf.test

by Ilya Buziuk (JIRA)

Ilya Buziuk created JBIDE-23065: ----------------------------------- Summary: test failure in org.jboss.tools.jsf.vpe.jsf.test Key: JBIDE-23065 URL: https://issues.jboss.org/browse/JBIDE-23065 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: visual-page-editor-templates Affects Versions: 4.4.1.AM3 Reporter: Ilya Buziuk Assignee: Ilya Buziuk Fix For: 4.4.1.Final Need to remove the following tests - http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... Those tests are also failing locally -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

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

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23039?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-23039: ----------------------------------- Priority: Critical (was: Major) > 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 > Priority: Critical > Fix For: 4.4.1.Final > > 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)

7 years, 7 months

1
0
0 / 0

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

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23039?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-23039: ----------------------------------- Fix Version/s: 4.4.1.Final > 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.1.Final > > 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)

7 years, 7 months

1
0
0 / 0

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

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23039?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-23039: ----------------------------------- Priority: Blocker (was: Critical) > 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 > Priority: Blocker > Fix For: 4.4.1.Final > > 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)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4032) [cdk installer] weird errors during startup

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-4032?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-4032: --------------------------------- Component/s: platform-installer (was: installer) > [cdk installer] weird errors during startup > ------------------------------------------- > > Key: JBDS-4032 > URL: https://issues.jboss.org/browse/JBDS-4032 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Reporter: Rob Stryker > > After a previously-working environment, I installed build http://cdk-builds.usersys.redhat.com/builds/nightly/devsuite/2016-08-24_0... > Once I did that, I get teh following environment: > Administrator@LBDZ-20120704HU MINGW64 /c/DevelopmentSuite4/cdk/components/rhel/rhel-ose > $ vagrant -v > Vagrant 1.8.1 > Administrator@LBDZ-20120704HU MINGW64 /c/DevelopmentSuite4/cdk/components/rhel/rhel-ose > $ vagrant plugin list > landrush (1.1.2) > vagrant-registration (1.2.2) > - Version Constraint: 1.2.2 > vagrant-service-manager (1.1.0) > - Version Constraint: 1.1.0 > vagrant-share (1.1.5, system) > vagrant-sshfs (1.1.0) > - Version Constraint: 1.1.0 > Vagrant up had following log: https://paste.fedoraproject.org/418594/77989147/ > That log indicated I should read another log. The 2nd log is: https://paste.fedoraproject.org/418595/26780201/ > Removing the box and re-adding it did not seem to help. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4031) Installer refuses to install cygwin

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4031?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-4031: ----------------------------------- Assignee: Denis Golovin > Installer refuses to install cygwin > ----------------------------------- > > Key: JBDS-4031 > URL: https://issues.jboss.org/browse/JBDS-4031 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.AM3 > Reporter: Jeff MAURY > Assignee: Denis Golovin > Fix For: 10.1.0.GA > > Attachments: install.log > > > I'm using devsuite-1.1.0-GA-20160831-126-installer.exe > The instaler refuses to install cygwin (for bad sha1 it seems) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4032) [cdk installer] weird errors during startup

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-4032?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-4032: --------------------------------- Issue Type: Bug (was: Feature Request) > [cdk installer] weird errors during startup > ------------------------------------------- > > Key: JBDS-4032 > URL: https://issues.jboss.org/browse/JBDS-4032 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Reporter: Rob Stryker > > After a previously-working environment, I installed build http://cdk-builds.usersys.redhat.com/builds/nightly/devsuite/2016-08-24_0... > Once I did that, I get teh following environment: > Administrator@LBDZ-20120704HU MINGW64 /c/DevelopmentSuite4/cdk/components/rhel/rhel-ose > $ vagrant -v > Vagrant 1.8.1 > Administrator@LBDZ-20120704HU MINGW64 /c/DevelopmentSuite4/cdk/components/rhel/rhel-ose > $ vagrant plugin list > landrush (1.1.2) > vagrant-registration (1.2.2) > - Version Constraint: 1.2.2 > vagrant-service-manager (1.1.0) > - Version Constraint: 1.1.0 > vagrant-share (1.1.5, system) > vagrant-sshfs (1.1.0) > - Version Constraint: 1.1.0 > Vagrant up had following log: https://paste.fedoraproject.org/418594/77989147/ > That log indicated I should read another log. The 2nd log is: https://paste.fedoraproject.org/418595/26780201/ > Removing the box and re-adding it did not seem to help. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4031) Installer refuses to install cygwin

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4031?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4031: -------------------------------- Story Points: 1 Sprint: devex #119 August 2016 > Installer refuses to install cygwin > ----------------------------------- > > Key: JBDS-4031 > URL: https://issues.jboss.org/browse/JBDS-4031 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.AM3 > Reporter: Jeff MAURY > Fix For: 10.1.0.GA > > Attachments: install.log > > > I'm using devsuite-1.1.0-GA-20160831-126-installer.exe > The instaler refuses to install cygwin (for bad sha1 it seems) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2016