September 2016 - jbosstools-issues

[JBoss JIRA] (JBTIS-846) Productize the JBDSIS/DevstudioIS stand-alone installers

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-846?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-846: ----------------------------- Summary: Productize the JBDSIS/DevstudioIS stand-alone installers (was: Productise the Devstudio IS stand-alone installer) > Productize the JBDSIS/DevstudioIS stand-alone installers > -------------------------------------------------------- > > Key: JBTIS-846 > URL: https://issues.jboss.org/browse/JBTIS-846 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 9.0.2.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 9.0.2.GA > > > The IS devstudio pom can now build a stand-alone installer. Modify any/all Jenkins jobs, product.yml, etc to handle productizing the installer. -- 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 Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23016?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-23016: ---------------------------------------- And we still have a potential problem with devstudio on all platforms if some input is required in terminal when starting CDK but this is covered in JBIDE-23039 > 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] (JBIDE-23016) When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23016?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-23016: ---------------------------------------- [~mmalina] thanks a lot! It's very helpful. So, we have a problem with landrush/devstudio only for Linux and Macs. > 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] (JBIDE-23131) Integration tests: move openshift integration tests to jbosstools/openshift repo

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23131?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-23131: ---------------------------------------- Do we really need the ability to run all integration tests manually by one command? Isn't it enough to be able to run integration tests per component + have all jenkins jobs set up properly so integration tests are run as part of the relevant builds/checks? > 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 > Time Spent: 4 hours > Remaining Estimate: 4 hours > > 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-22806) Connection wizard: "Finish" is enabled even though I didnt oauth authenticate to pick a token

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22806?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22806: ------------------------------------------ tested it, works for me. Merged the PR into master. > Connection wizard: "Finish" is enabled even though I didnt oauth authenticate to pick a token > --------------------------------------------------------------------------------------------- > > Key: JBIDE-22806 > URL: https://issues.jboss.org/browse/JBIDE-22806 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Andre Dietisheim > Assignee: Jeff MAURY > Priority: Minor > Labels: connection_wizard, openshift_v3 > Fix For: 4.4.2.AM1 > > Attachments: connection-page-finish-enabled.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23143) Cannot install JBoss Tools 4.4.1.Final into Eclipse Neon.1 RC2

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23143?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-23143: ---------------------------------------- [~xcoulon] : {quote}{code}Cannot satisfy dependency: From: JBoss WebServices Tools 1.9.1.v20160608-0648 (org.jboss.tools.ws.feature.feature.group 1.9.1.v20160608-0648) To: org.eclipse.wst.web_ui.feature.feature.group [3.3.2,4.0.0){code} We should confirm that the features and plugins in o.j.t.ws. feature don't require a too-restrictive version of anything from webtools, ie, that could cause the error above. Cc: @xcoulon{quote} > Cannot install JBoss Tools 4.4.1.Final into Eclipse Neon.1 RC2 > -------------------------------------------------------------- > > Key: JBIDE-23143 > URL: https://issues.jboss.org/browse/JBIDE-23143 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, updatesite, upstream > Affects Versions: 4.4.1.Final > Reporter: Martin Malina > Assignee: Mickael Istria > Attachments: neon-1-byoe.png, neon-1-remediation.png, update-sites-enabled.png > > > When I try to install JBoss Tools 4.4.1.Final [1] Abridged category into eclipse-java-neon-1-RC2-macosx-cocoa-x86_64.tar.gz , I am shown a remediation screen. > !neon-1-remediation.png! > If I choose Update my installation, it offers to install what I want, but uninstall Eclipse XML Editors and Tools. > This is the original error message (third option): > {code} > Your original request has been modified. > "Code Recommenders Snipmatch" will be ignored because a newer version is already installed. > Cannot complete the install because of a conflicting dependency. > Software being installed: JBoss WebServices Tools 1.9.1.v20160608-0648 (org.jboss.tools.ws.feature.feature.group 1.9.1.v20160608-0648) > Software currently installed: Eclipse XML Editors and Tools 3.9.0.v201608061824 (org.eclipse.wst.xml_ui.feature.feature.group 3.9.0.v201608061824) > Only one of the following can be installed at once: > Eclipse XML Editors and Tools 3.8.0.v201605120129 (org.eclipse.wst.xml_ui.feature.feature.jar 3.8.0.v201605120129) > Eclipse XML Editors and Tools 3.9.0.v201608061824 (org.eclipse.wst.xml_ui.feature.feature.jar 3.9.0.v201608061824) > Cannot satisfy dependency: > From: Eclipse Web Developer Tools 3.8.0.v201606030549 (org.eclipse.wst.web_ui.feature.feature.group 3.8.0.v201606030549) > To: org.eclipse.wst.xml_ui.feature.feature.group [3.8.0.v201605120129] > Cannot satisfy dependency: > From: Eclipse XML Editors and Tools 3.8.0.v201605120129 (org.eclipse.wst.xml_ui.feature.feature.group 3.8.0.v201605120129) > To: org.eclipse.wst.xml_ui.feature.feature.jar [3.8.0.v201605120129] > Cannot satisfy dependency: > From: Eclipse XML Editors and Tools 3.9.0.v201608061824 (org.eclipse.wst.xml_ui.feature.feature.group 3.9.0.v201608061824) > To: org.eclipse.wst.xml_ui.feature.feature.jar [3.9.0.v201608061824] > Cannot satisfy dependency: > From: JBoss WebServices Tools 1.9.1.v20160608-0648 (org.jboss.tools.ws.feature.feature.group 1.9.1.v20160608-0648) > To: org.eclipse.wst.web_ui.feature.feature.group [3.3.2,4.0.0) > {code} > [1] http://download.jboss.org/jbosstools/neon/staging/updates/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2360) Login quickstart generates warnings

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-2360?page=com.atlassian.jira.plugin.... ] Alexey Kazakov resolved JBDS-2360. ---------------------------------- Resolution: Out of Date > Login quickstart generates warnings > ----------------------------------- > > Key: JBDS-2360 > URL: https://issues.jboss.org/browse/JBDS-2360 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central > Affects Versions: 6.0.0.Alpha2 > Environment: Version: 6.0.0.Alpha2 > Build id: Alpha2-v20121004-2330-B40 > Build date: 20121004-2330 > Reporter: Len DiMaggio > Assignee: Marius Bogoevici > Labels: examplewarnings > Fix For: 6.0.2.GA > > > The Login quickstart generates these warnings: > No connection specified for project. No database-specific validation will be performed. > jboss-as-login > Unnecessary @SuppressWarnings("unused") > Resources.java > /jboss-as-login/src/main/java/org/jboss/as/quickstarts/login > line 13 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-1966) properties editor very slow

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-1966?page=com.atlassian.jira.plugin... ] Alexey Kazakov resolved JBIDE-1966. ----------------------------------- Fix Version/s: 4.0.0.Final (was: LATER) Resolution: Done > properties editor very slow > --------------------------- > > Key: JBIDE-1966 > URL: https://issues.jboss.org/browse/JBIDE-1966 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 2.0.0.GA > Reporter: Martin Trummer > Assignee: Viacheslav Kabanovich > Fix For: 4.0.0.Final > > Attachments: DummyMessages.properties > > > unfortunately I can't provide a recipe to reproduce the problem. > However: It seems to happen when: > I open 2 properties files - each about 300 lines > I have the properties files open for some time (not using it) > then I add a line and save it: in this case eclipse is stuck for 1-2 seconds. > I only have about 300 properties in the editor. -- 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 Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23131?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-23131: ------------------------------------ +1 > 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 > Time Spent: 4 hours > Remaining Estimate: 4 hours > > 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-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: ------------------------------------- To be clear: the problem on windows is that the user's input is not visible. The terminal still shows correct output but the user is not seeing their input displayed. I will investigate whether a flag is missing somewhere. > 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