September 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23089) when central tests crash job breaks due to dirty workspace

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23089?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23089: ------------------------------- Fix Version/s: 4.4.2.AM1 > when central tests crash job breaks due to dirty workspace > ---------------------------------------------------------- > > Key: JBIDE-23089 > URL: https://issues.jboss.org/browse/JBIDE-23089 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central > Affects Versions: 4.4.1.Final, 4.4.2.AM1 > Reporter: Nick Boldt > Fix For: 4.4.2.AM1 > > > {code} > 15:00:03 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.26.0:build-qualifier (default-build-qualifier) on project org.jboss.tools.central.test: Working tree is dirty. > 15:00:03 [ERROR] git status central/tests/org.jboss.tools.central.test: > 15:00:03 [ERROR] > 15:00:03 [ERROR] Untracked files: > 15:00:03 [ERROR] central/tests/org.jboss.tools.central.test/hs_err_pid29878.log > 15:00:03 [ERROR] > 15:00:03 [ERROR] You are trying to use tycho-buildtimestamp-jgit on a directory that has uncommitted changes (see details above). > 15:00:03 [ERROR] Either commit all changes/add files to .gitignore, or enable fallback to default timestamp provider by configuring > 15:00:03 [ERROR] jgit.dirtyWorkingTree=warning for tycho-packaging-plugin{code} > -- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > Workaround: > wipe workspace, try again > Solution: > add hs_err_pid*.log to .gitignore -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23147) Support optional host when route is created

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-23147: ---------------------------------- Summary: Support optional host when route is created Key: JBIDE-23147 URL: https://issues.jboss.org/browse/JBIDE-23147 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.4.1.Final Reporter: Jeff MAURY Fix For: 4.4.2.AM2 When an application is created and route option is selected, the host is generated by default but user should have the option to set it (as in web console) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23147) Support optional host when route is created

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23147?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23147: ------------------------------- Labels: openshift openshift_v3 (was: ) > Support optional host when route is created > ------------------------------------------- > > Key: JBIDE-23147 > URL: https://issues.jboss.org/browse/JBIDE-23147 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Jeff MAURY > Labels: openshift, openshift_v3 > Fix For: 4.4.2.AM2 > > > When an application is created and route option is selected, the host is generated by default but user should have the option to set it (as in web console) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23146) Add missing $NON-NLS-1$ tags in org.jboss.tools.hibernate.ui.xml.editor.HibernatePropertiesContentAssistProcessor

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23146?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-23146: ------------------------------ Fix Version/s: 4.4.2.AM1 > Add missing $NON-NLS-1$ tags in org.jboss.tools.hibernate.ui.xml.editor.HibernatePropertiesContentAssistProcessor > ----------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23146 > URL: https://issues.jboss.org/browse/JBIDE-23146 > 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-23146) Add missing $NON-NLS-1$ tags in org.jboss.tools.hibernate.ui.xml.editor.HibernatePropertiesContentAssistProcessor

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23146?page=com.atlassian.jira.plugi... ] Koen Aers reassigned JBIDE-23146: --------------------------------- Assignee: Koen Aers > Add missing $NON-NLS-1$ tags in org.jboss.tools.hibernate.ui.xml.editor.HibernatePropertiesContentAssistProcessor > ----------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23146 > URL: https://issues.jboss.org/browse/JBIDE-23146 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.4.1.Final > Reporter: Koen Aers > Assignee: Koen Aers > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23146) Add missing $NON-NLS-1$ tags in org.jboss.tools.hibernate.ui.xml.editor.HibernatePropertiesContentAssistProcessor

by Koen Aers (JIRA)

Koen Aers created JBIDE-23146: --------------------------------- Summary: Add missing $NON-NLS-1$ tags in org.jboss.tools.hibernate.ui.xml.editor.HibernatePropertiesContentAssistProcessor Key: JBIDE-23146 URL: https://issues.jboss.org/browse/JBIDE-23146 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] (JBTIS-850) Improve stability of adding a new connection

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/JBTIS-850?page=com.atlassian.jira.plugin.... ] Jozef Marko commented on JBTIS-850: ----------------------------------- Problem with devices with small screens. There was not need to update org.jboss.tools.bpmn2.reddeer plugin. > Improve stability of adding a new connection > -------------------------------------------- > > Key: JBTIS-850 > URL: https://issues.jboss.org/browse/JBTIS-850 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: BPMN2, QE > Affects Versions: 4.3.1.Final > Reporter: Andrej Podhradsky > Assignee: Jozef Marko > > It seems that the logic for adding a new connection between two components doesn't always work. Please see the error which occured on jawa34g1 > {code} > org.jboss.tools.bpmn2.ui.bot.complex.test.testcase.ComplexParalellSplitJoinTest.jbpm6ComplexTest default (from org.jboss.tools.bpmn2.ui.bot.test.SmokeTests) > Failing for the past 4 builds (Since Unstable#320 ) > Took 30 sec. > add description > Error Message > Timeout after: 10 s.: the number of edit parts is 37 > Stacktrace > org.jboss.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 10 s.: the number of edit parts is 37 > at org.jboss.reddeer.common.wait.AbstractWait.timeoutExceeded(AbstractWait.java:173) > at org.jboss.reddeer.common.wait.AbstractWait.wait(AbstractWait.java:126) > at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:91) > at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:61) > at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:46) > at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:34) > at org.jboss.reddeer.common.wait.WaitUntil.<init>(WaitUntil.java:25) > at org.jboss.tools.bpmn2.reddeer.GEFProcessEditor.addConnectionFromPalette(GEFProcessEditor.java:136) > at org.jboss.tools.bpmn2.reddeer.editor.Element$ConnectionAdded.test(Element.java:567) > at org.jboss.reddeer.common.wait.WaitUntil.stopWaiting(WaitUntil.java:80) > at org.jboss.reddeer.common.wait.AbstractWait.wait(AbstractWait.java:122) > at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:91) > at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:61) > at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:46) > at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:34) > at org.jboss.reddeer.common.wait.WaitUntil.<init>(WaitUntil.java:25) > at org.jboss.tools.bpmn2.reddeer.editor.Element.connectTo(Element.java:298) > at org.jboss.tools.bpmn2.reddeer.editor.Element.connectTo(Element.java:287) > at org.jboss.tools.bpmn2.ui.bot.complex.test.testcase.ComplexParalellSplitJoinTest.model(ComplexParalellSplitJoinTest.java:54) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-414) Docker Image View: Build Image and Pull Image toolbar icons not enabled/disabled properly [EBZ#501175]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-414: --------------------------------------- Summary: Docker Image View: Build Image and Pull Image toolbar icons not enabled/disabled properly [EBZ#501175] Key: ERT-414 URL: https://issues.jboss.org/browse/ERT-414 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot Fix For: Neon.1 (4.6) The toolbar icons for Build Image and Pull Image should be enabled when an established connection is selected in the Docker Explorer View and should be disabled when no active/established connection is selected in the view. -- 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 Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23039?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-23039: ------------------------------------- So I made a very simple java class with the following main method: {code} public class SimpleIO { public static void main(String[] args) { BufferedReader br = new BufferedReader(new InputStreamReader(System.in)); try { System.out.println("Hello, what is your name? "); String input = br.readLine(); System.out.println("Hello " + input + ", how old are you? "); input = br.readLine(); System.out.println("Wow, so old!"); } catch(IOException ioe) { } finally { try { br.close(); } catch(IOException ioe){} } } } {code} I then compiled this simple class, placed it somewhere, and modified my CDK Launch code to call "java SimpleIO" in the proper working directory, and link to the terminal (same as I do now with the vagrant up command). It works 100% as expected in the case of this SimpleIO class. Input is recognized immediately, the simple class is responsive to my pressing of enter, and everything seems to work as expected. But it fails miserably (on windows) when doing vagrant up and passing input to the registration plugin. > 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-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: ------------------------------------- OK... I managed to find a flag to make the text visible... however... it doesnt seem to fix any of the other issues you found. The streams don't respond to pressing enter once, and once you press it a second time, it moves on past where you'd expect it to in the conversation. > 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

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