September 2016 - jbosstools-issues

[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: Major (was: Blocker) > 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-23115) Usage Analytics New and Noteworthy for 4.4.1.Final

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23115?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-23115. ---------------------------------- Resolution: Rejected No N&N > Usage Analytics New and Noteworthy for 4.4.1.Final > -------------------------------------------------- > > Key: JBIDE-23115 > URL: https://issues.jboss.org/browse/JBIDE-23115 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: usage > Reporter: Jeff MAURY > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.4.1.Final > > > If no news for 4.4.1.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate <component>-news-4.4.1.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new <component>-news-4.4.1.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...], add "page-include-previous: false" attribute to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23120) CDI New and Noteworthy for 4.4.1.Final

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23120?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-23120. ---------------------------------- Resolution: Rejected No N&N > CDI New and Noteworthy for 4.4.1.Final > -------------------------------------- > > Key: JBIDE-23120 > URL: https://issues.jboss.org/browse/JBIDE-23120 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdi > Reporter: Jeff MAURY > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.4.1.Final > > > If no news for 4.4.1.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate <component>-news-4.4.1.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new <component>-news-4.4.1.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...], add "page-include-previous: false" attribute to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23099) jst/jsf New and Noteworthy for 4.4.1.Final

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23099?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-23099. ---------------------------------- Release Notes Text: No N&N Resolution: Rejected > jst/jsf New and Noteworthy for 4.4.1.Final > ------------------------------------------ > > Key: JBIDE-23099 > URL: https://issues.jboss.org/browse/JBIDE-23099 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsf, jsp/jsf/xml/html-source-editing > Reporter: Jeff MAURY > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.4.1.Final > > > If no news for 4.4.1.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate <component>-news-4.4.1.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new <component>-news-4.4.1.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...], add "page-include-previous: false" attribute to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23113) Batch New and Noteworthy for 4.4.1.Final

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23113?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-23113. ---------------------------------- Resolution: Rejected No N&N > Batch New and Noteworthy for 4.4.1.Final > ---------------------------------------- > > Key: JBIDE-23113 > URL: https://issues.jboss.org/browse/JBIDE-23113 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: batch > Reporter: Jeff MAURY > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.4.1.Final > > > If no news for 4.4.1.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate <component>-news-4.4.1.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new <component>-news-4.4.1.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...], add "page-include-previous: false" attribute to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23095) Add missing error notificators into design view for elements with ids.

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23095?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-23095: ----------------------------------- Fix Version/s: 4.4.x > Add missing error notificators into design view for elements with ids. > ---------------------------------------------------------------------- > > Key: JBIDE-23095 > URL: https://issues.jboss.org/browse/JBIDE-23095 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: batch > Affects Versions: 4.4.1.Final > Reporter: Ondrej Dockal > Fix For: 4.4.x > > Attachments: BatchNoValidationDesignTab.png, BatchValidationOfIDSourceTab.png > > > I noticed missing error notifications (small error icons used for example at ref. attributes) when working with design view elements like step/flow/decision that have an id attribute. In source view we can see there is an error on line where id is duplicated, but not in design view, see attachments (source view: error icon on second occurence of my-step-listener, in design view this does not work). > P.S. Do not notice duplicated messages in Problem view, it's been already reported. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23124) install grinder fails pulling files from eclipse mirrors (instead of using JBT mirrors / TP)

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-23124: ---------------------------------- Summary: install grinder fails pulling files from eclipse mirrors (instead of using JBT mirrors / TP) Key: JBIDE-23124 URL: https://issues.jboss.org/browse/JBIDE-23124 Project: Tools (JBoss Tools) Issue Type: Bug Components: build, install-tests Affects Versions: 4.4.1.Final Reporter: Nick Boldt {code} 20:18:21 !ENTRY org.eclipse.equinox.p2.transport.ecf 2 0 2016-09-02 20:18:21.888 20:18:21 !MESSAGE Connection to http://mirror.lagoon.nc/pub/eclipse/tools/orbit/downloads/drops/R20150821... failed on Connection refused. Retry attempt 0 started {code} -- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/devs... {code} 20:21:57 !MESSAGE Connection to http://mirror.lagoon.nc/pub/eclipse/tools/orbit/downloads/drops/R20150821... failed on Connection refused. Retry attempt 0 started {code} -- https://jenkins.mw.lab.eng.bos.redhat.comhttps://jenkins.mw.lab.eng.bos.r... and {code} 20:32:38 !MESSAGE Connection to http://mirror.lagoon.nc/pub/eclipse/releases/neon/201606221000/plugins/or... failed on Connection refused. Retry attempt 0 started {code} https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/devs... Should we be ignoring these failures? Should the install process be using eclipse mirrors? Or should we be installing against TPs under http://download.jboss.org/jbosstools/targetplatforms/ or our mirrors under http://download.jboss.org/jbosstools/updates/requirements/ ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23124) install grinder fails pulling files from eclipse mirrors (instead of using JBT mirrors / TP)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23124?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23124: ------------------------------- Fix Version/s: 4.4.2.AM1 > install grinder fails pulling files from eclipse mirrors (instead of using JBT mirrors / TP) > -------------------------------------------------------------------------------------------- > > Key: JBIDE-23124 > URL: https://issues.jboss.org/browse/JBIDE-23124 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, install-tests > Affects Versions: 4.4.1.Final > Reporter: Nick Boldt > Fix For: 4.4.2.AM1 > > > {code} > 20:18:21 !ENTRY org.eclipse.equinox.p2.transport.ecf 2 0 2016-09-02 20:18:21.888 > 20:18:21 !MESSAGE Connection to http://mirror.lagoon.nc/pub/eclipse/tools/orbit/downloads/drops/R20150821... failed on Connection refused. Retry attempt 0 started > {code} > -- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/devs... > {code} > 20:21:57 !MESSAGE Connection to http://mirror.lagoon.nc/pub/eclipse/tools/orbit/downloads/drops/R20150821... failed on Connection refused. Retry attempt 0 started > {code} > -- https://jenkins.mw.lab.eng.bos.redhat.comhttps://jenkins.mw.lab.eng.bos.r... > and > {code} > 20:32:38 !MESSAGE Connection to http://mirror.lagoon.nc/pub/eclipse/releases/neon/201606221000/plugins/or... failed on Connection refused. Retry attempt 0 started > {code} > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/devs... > Should we be ignoring these failures? Should the install process be using eclipse mirrors? Or should we be installing against TPs under http://download.jboss.org/jbosstools/targetplatforms/ or our mirrors under http://download.jboss.org/jbosstools/updates/requirements/ ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23124) install grinder fails pulling files from eclipse mirrors (instead of using JBT mirrors / TP)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23124?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-23124: ---------------------------------- Assignee: Mickael Istria > install grinder fails pulling files from eclipse mirrors (instead of using JBT mirrors / TP) > -------------------------------------------------------------------------------------------- > > Key: JBIDE-23124 > URL: https://issues.jboss.org/browse/JBIDE-23124 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, install-tests > Affects Versions: 4.4.1.Final > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.4.2.AM1 > > > {code} > 20:18:21 !ENTRY org.eclipse.equinox.p2.transport.ecf 2 0 2016-09-02 20:18:21.888 > 20:18:21 !MESSAGE Connection to http://mirror.lagoon.nc/pub/eclipse/tools/orbit/downloads/drops/R20150821... failed on Connection refused. Retry attempt 0 started > {code} > -- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/devs... > {code} > 20:21:57 !MESSAGE Connection to http://mirror.lagoon.nc/pub/eclipse/tools/orbit/downloads/drops/R20150821... failed on Connection refused. Retry attempt 0 started > {code} > -- https://jenkins.mw.lab.eng.bos.redhat.comhttps://jenkins.mw.lab.eng.bos.r... > and > {code} > 20:32:38 !MESSAGE Connection to http://mirror.lagoon.nc/pub/eclipse/releases/neon/201606221000/plugins/or... failed on Connection refused. Retry attempt 0 started > {code} > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/devs... > Should we be ignoring these failures? Should the install process be using eclipse mirrors? Or should we be installing against TPs under http://download.jboss.org/jbosstools/targetplatforms/ or our mirrors under http://download.jboss.org/jbosstools/updates/requirements/ ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23124) install grinder fails pulling files from eclipse mirrors (instead of using JBT mirrors / TP)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23124?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23124: ------------------------------------ [~mickael_istria] Would you mind looking at why install-grinder is doing this, and suggesting what we can do to avoid it? Thanks! > install grinder fails pulling files from eclipse mirrors (instead of using JBT mirrors / TP) > -------------------------------------------------------------------------------------------- > > Key: JBIDE-23124 > URL: https://issues.jboss.org/browse/JBIDE-23124 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, install-tests > Affects Versions: 4.4.1.Final > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.4.2.AM1 > > > {code} > 20:18:21 !ENTRY org.eclipse.equinox.p2.transport.ecf 2 0 2016-09-02 20:18:21.888 > 20:18:21 !MESSAGE Connection to http://mirror.lagoon.nc/pub/eclipse/tools/orbit/downloads/drops/R20150821... failed on Connection refused. Retry attempt 0 started > {code} > -- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/devs... > {code} > 20:21:57 !MESSAGE Connection to http://mirror.lagoon.nc/pub/eclipse/tools/orbit/downloads/drops/R20150821... failed on Connection refused. Retry attempt 0 started > {code} > -- https://jenkins.mw.lab.eng.bos.redhat.comhttps://jenkins.mw.lab.eng.bos.r... > and > {code} > 20:32:38 !MESSAGE Connection to http://mirror.lagoon.nc/pub/eclipse/releases/neon/201606221000/plugins/or... failed on Connection refused. Retry attempt 0 started > {code} > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/devs... > Should we be ignoring these failures? Should the install process be using eclipse mirrors? Or should we be installing against TPs under http://download.jboss.org/jbosstools/targetplatforms/ or our mirrors under http://download.jboss.org/jbosstools/updates/requirements/ ? -- 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