September 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-4042) Div element of error message is not wrapped

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4042?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-4042. ----------------------------- Verified in build 132. > Div element of error message is not wrapped > ------------------------------------------- > > Key: JBDS-4042 > URL: https://issues.jboss.org/browse/JBDS-4042 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 1.1.0.GA > Environment: Win 10 x86_64, devsuite-1.1.0-GA-20160902-131-bundle-installer.exe > Reporter: Ondrej Dockal > Assignee: Denis Golovin > Attachments: platform_installer.PNG > > > Error message used when user name contains space in his name is not wrapped. See attachment. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23096) Remove the definition and uses of class org.jboss.tools.hibernate.runtime.spi.IHibernateMappingGlobalSettings

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23096?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-23096: ------------------------------ Fix Version/s: 4.4.2.AM1 (was: 4.5.0.AM1) > Remove the definition and uses of class org.jboss.tools.hibernate.runtime.spi.IHibernateMappingGlobalSettings > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23096 > URL: https://issues.jboss.org/browse/JBIDE-23096 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.4.1.Final > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.2.AM1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23096) Remove the definition and uses of class org.jboss.tools.hibernate.runtime.spi.IHibernateMappingGlobalSettings

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23096?page=com.atlassian.jira.plugi... ] Koen Aers reassigned JBIDE-23096: --------------------------------- Fix Version/s: 4.5.0.AM1 Assignee: Koen Aers > Remove the definition and uses of class org.jboss.tools.hibernate.runtime.spi.IHibernateMappingGlobalSettings > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23096 > URL: https://issues.jboss.org/browse/JBIDE-23096 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.4.1.Final > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.5.0.AM1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23096) Remove the definition and uses of class org.jboss.tools.hibernate.runtime.spi.IHibernateMappingGlobalSettings

by Koen Aers (JIRA)

Koen Aers created JBIDE-23096: --------------------------------- Summary: Remove the definition and uses of class org.jboss.tools.hibernate.runtime.spi.IHibernateMappingGlobalSettings Key: JBIDE-23096 URL: https://issues.jboss.org/browse/JBIDE-23096 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, 7 months

1
0
0 / 0

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

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23039?page=com.atlassian.jira.plugi... ] Roland Grunberg commented on JBIDE-23039: ----------------------------------------- So it looks like 'script' on MacOS doesn't have an "-f/--flush" option. [~rob.stryker] , is there enough time to try simply without that option and see if it works and test on MacOS. > 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)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23043) Not working connection to CDK Docker deamon

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23043?page=com.atlassian.jira.plugi... ] Jeff Johnston resolved JBIDE-23043. ----------------------------------- Resolution: Done > Not working connection to CDK Docker deamon > ------------------------------------------- > > Key: JBIDE-23043 > URL: https://issues.jboss.org/browse/JBIDE-23043 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, docker, target-platform > Affects Versions: 4.4.1.Final > Environment: F24, > Devstudio: > Version: 10.1.0.GA > Build id: GA-v20160825-0621-B5857 > Build date: 20160825-0621 > Docker Tooling: > 2.1.0.20160825102 > Reporter: Josef Kopriva > Assignee: Jeff Johnston > Priority: Blocker > Fix For: 4.4.1.Final > > Attachments: RC1vs0825N.txt, RC1vs0825N_sorted.txt > > > After upgrading Docker Tooling to latest nightly, I cannot create connection to the Docker CDK deamon through TCP connection with certificates. > Stacktrace: > {code:java} > An internal error occurred during: "Opening connection...". > java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMParser > at com.spotify.docker.client.DockerCertificates.<init>(DockerCertificates.java:80) > at com.spotify.docker.client.DockerCertificates.<init>(DockerCertificates.java:64) > at org.eclipse.linuxtools.internal.docker.core.DockerClientFactory.getClient(DockerClientFactory.java:83) > at org.eclipse.linuxtools.internal.docker.core.DockerClientFactory.getClient(DockerClientFactory.java:47) > at org.eclipse.linuxtools.internal.docker.core.DockerConnection.open(DockerConnection.java:252) > at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerContentProvider$1.run(DockerExplorerContentProvider.java:179) > 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

1
0
0 / 0

[JBoss JIRA] (JBTIS-849) Completely disable AERI in all tests

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-849: --------------------------------------- Summary: Completely disable AERI in all tests Key: JBTIS-849 URL: https://issues.jboss.org/browse/JBTIS-849 Project: JBoss Tools Integration Stack Issue Type: Task Components: QE Affects Versions: 4.3.1.Final Reporter: Andrej Podhradsky Assignee: Andrej Podhradsky Fix For: 4.3.1.Final Almost all tests rely on on the fact that a running job is completed in some reasonable time. This doesn't apply for the job "Updating Error Reports Database" which sometimes never finishes and must be killed (a test doesn't know that this job can be killed). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4035) Missing uninstall.ps1 script

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4035?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-4035. ----------------------------- Verified in build 132. > Missing uninstall.ps1 script > ---------------------------- > > Key: JBDS-4035 > URL: https://issues.jboss.org/browse/JBDS-4035 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.AM3 > Environment: *Windows 10* > Reporter: Lukáš Valach > Assignee: Denis Golovin > Fix For: 10.1.0.GA > > > Platform installer doesn't copies the uninstall.ps1 script to the TARGET_FOLTER/uninstall/ directory when the target folder already exists. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[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: --------------------------------------- I suggest we revert this commit as it is currently not needed for Alpina - CDK 2.2 rc3 removed landrush. And for the next sprint in master, we can spend more time on fixing this properly. > 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)

9 years, 7 months

1
0
0 / 0

[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 edited comment on JBIDE-23039 at 9/2/16 8:30 AM: --------------------------------------------------------------- Now I cannot start cdk at all :( I just installed devstudio [1] on Mac, launched it, added cdk 2.2 rc3 and then tried to start. I got an error in the error log view: Server Container Development Environment failed to start. An exception stack trace is not available. Terminal view was opened and this was inside: {code} /usr/bin/script: illegal option -- f usage: script [-adkpqr] [-t time] [file [command ...]] {code} As you can see, the option -f is not supported in this Mac version of /usr/bin/script. BTW, even if this worked, is it intentional that we will now use the terminal view instead of console? Or will both be used? It could be confusing. And note that in most cases no input will be needed (especially now with landrush removed for cdk 2.2). [1] devstudio-10.1.0.GA-v20160901-1658-B5921-installer-standalone.jar was (Author: mmalina): Now I cannot start cdk at all :( I just installed devstudio [1], launched it, added cdk 2.2 rc3 and then tried to start. I got an error in the error log view: Server Container Development Environment failed to start. An exception stack trace is not available. Terminal view was opened and this was inside: {code} /usr/bin/script: illegal option -- f usage: script [-adkpqr] [-t time] [file [command ...]] {code} BTW, even if this worked, is it intentional that we will now use the terminal view instead of console? Or will both be used? It could be confusing. And note that in most cases no input will be needed (especially now with landrush removed for cdk 2.2). [1] devstudio-10.1.0.GA-v20160901-1658-B5921-installer-standalone.jar > 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)

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