May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20442) Create SWTBot integration tests for tern related features

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20442?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-20442: ------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.3.x) > Create SWTBot integration tests for tern related features > --------------------------------------------------------- > > Key: JBIDE-20442 > URL: https://issues.jboss.org/browse/JBIDE-20442 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Beta2 > Reporter: Denis Golovin > Assignee: Pavol Srna > Priority: Critical > Fix For: 4.4.0.Alpha2 > > > There should be set of SWTBot tests that would cover functionality related to tern.java and angularjs-eclipse integration. These tests would simplify migration to new tern.java and angularjs-eclipse releases. > Current process for migration to new version of tern-java/angularjs-eclipse is manual. Steps below describe current approach: > 1. Manual mirroring of latest tern-java/angularjs-eclipse versions to local filesystem; > 2. Build jbosstools-jst with local mirrors and run JUnit tests; > 3. Install latest tern-java and angularjs-eclipse form mirrors done in (1) into JBDS nightly build from master branch (it has open version range for tern features) and restart; > 4. Run manual tests; > 5. If (2) and (3) idenify no problems then local mirrors should be published to http://download.jboss.org/jbosstools/updates/requirements/tern and http://download.jboss.org/jbosstools/updates/requirements/angularjs respectively; > 6. Update jbosstools-jst with new versions for tern-java/angularjs-eclipse and push local branch to upstream > With step 4 implemented as SWT bot tests and automated mirroring for tern-java and angularjs-eclipse (see jenkins job here https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/All/job/jbosstools-...) we can fully automate the process above. > QA also can skip step (1) and just use external p2 repos: > * http://oss.opensagres.fr/tern.repository/1.0.0-SNAPSHOT/ > * http://oss.opensagres.fr/angularjs-eclipse/1.0.0-SNAPSHOT/ > in step (2) by building jbosstools-jst as: > {code}mvn clean install -Dtern.repo.url=http://oss.opensagres.fr/tern.repository/1.0.0-SNAPSHOT/ -Dhttp://oss.opensagres.fr/angularjs-eclipse/1.0.0-SNAPSHOT/{code} > and installing latest versions for step (3). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3787) Installer - Installation of each component should be optional

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3787?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3787: ------------------------------------- Attached [^screenshot-1.png] from my local POC. > Installer - Installation of each component should be optional > ------------------------------------------------------------- > > Key: JBDS-3787 > URL: https://issues.jboss.org/browse/JBDS-3787 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.Alpha3 > > Attachments: components are optional v1.png, components are optional v2.png, screenshot-1.png > > > Feature request - It would be ideal of the installer allowed to the user to select to install/not install any of the installer's components (JDK, CDK, etc.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3787) Installer - Installation of each component should be optional

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3787?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3787: -------------------------------- Attachment: screenshot-1.png > Installer - Installation of each component should be optional > ------------------------------------------------------------- > > Key: JBDS-3787 > URL: https://issues.jboss.org/browse/JBDS-3787 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.Alpha3 > > Attachments: components are optional v1.png, components are optional v2.png, screenshot-1.png > > > Feature request - It would be ideal of the installer allowed to the user to select to install/not install any of the installer's components (JDK, CDK, etc.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3787) Installer - Installation of each component should be optional

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3787?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3787: ------------------------------------- Also components like Cygwin are are going to be optional for installation, but still we have to show warning about it being required for CDK to run. > Installer - Installation of each component should be optional > ------------------------------------------------------------- > > Key: JBDS-3787 > URL: https://issues.jboss.org/browse/JBDS-3787 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.Alpha3 > > Attachments: components are optional v1.png, components are optional v2.png > > > Feature request - It would be ideal of the installer allowed to the user to select to install/not install any of the installer's components (JDK, CDK, etc.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3787) Installer - Installation of each component should be optional

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3787?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3787: ------------------------------------- [~joqian] thanks for update, I have POC implementation for new UI it implements your design as close as possible. In current implementation released in April we actually print out detected version and exact message is '\/ Using detected version 1.7.4', I think we should show both messages: '\/ Using detected version 1.7.4' '/!\ Newer than suported' > Installer - Installation of each component should be optional > ------------------------------------------------------------- > > Key: JBDS-3787 > URL: https://issues.jboss.org/browse/JBDS-3787 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.Alpha3 > > Attachments: components are optional v1.png, components are optional v2.png > > > Feature request - It would be ideal of the installer allowed to the user to select to install/not install any of the installer's components (JDK, CDK, etc.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-709) JBDS 9.1 GA: Document a use case for Forge Tooling

by Supriya Bharadwaj (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-709?page=com.atlassian.jira.plug... ] Supriya Bharadwaj updated TOOLSDOC-709: --------------------------------------- Attachment: forge_start_button.png forge_new_project.png forge_new_entity_in_editor.png forge_link_with_editor_button.png forge_generate_scaffold.png forge_addon_in_context_menu.png forge_add_fields_to_entity.png forge_add_command.png forge.adoc Hi [~mhusnain], can you please post the article upstream. Thanks! > JBDS 9.1 GA: Document a use case for Forge Tooling > -------------------------------------------------- > > Key: TOOLSDOC-709 > URL: https://issues.jboss.org/browse/TOOLSDOC-709 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Components: General documentation issues > Affects Versions: 9.1 GA > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Labels: Forge > Fix For: 9.1 GA > > Attachments: forge.adoc, forge_addon_in_context_menu.png, forge_add_command.png, forge_add_fields_to_entity.png, forge_generate_scaffold.png, forge_link_with_editor_button.png, forge_new_entity_in_editor.png, forge_new_project.png, forge_start_button.png > > > Document a use case for Forge tooling. > 1. Draft a potential use case for what users may want to do with forge. > 2. Get review on use case idea from a relevant SME or QE person > 3. Write an intro and flesh out the use case with relevant screenshots > 4. Get QE review > 5. Create upstream and downstream versions of approved content. > a. Add CSP version to customer portal > b. Send Misha upstream version -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3627) Installer needs to help move past lack of t/c signing

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3627: -------------------------------- Sprint: devex #115 May 2016 (was: devex #114 May 2016) > Installer needs to help move past lack of t/c signing > ----------------------------------------------------- > > Key: JBDS-3627 > URL: https://issues.jboss.org/browse/JBDS-3627 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Enhancement > Components: platform-installer > Reporter: Joshua Wilson > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.Alpha3 > > Attachments: Installer-not-signed-tc.PNG > > > When you login with an active account that hasn't signed the Terms and Conditions the login fails and tells you why but not how to resolve it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3618) Progress does not reflect actual amount of work done

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3618?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3618: -------------------------------- Sprint: devex #115 May 2016 (was: devex #114 May 2016) > Progress does not reflect actual amount of work done > ---------------------------------------------------- > > Key: JBDS-3618 > URL: https://issues.jboss.org/browse/JBDS-3618 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: platform-installer > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Minor > Labels: havoc, ui > Fix For: 10.0.0.Alpha3 > > > It seems the current way the progress tracking is implemented is simply by giving an initial time estimate for each component. The progress bars then just count down the supplied time with no relation to the actual progress achieved. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22390) Forge New and Noteworthy for 4.4.0.Alpha2

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22390?page=com.atlassian.jira.plugi... ] George Gastaldi commented on JBIDE-22390: ----------------------------------------- Hi [~akazakov], I´m sorry, I am on vacation until May 30th. I think the only N&N is the runtime upgrade to 3.2.0.Final. > Forge New and Noteworthy for 4.4.0.Alpha2 > ----------------------------------------- > > Key: JBIDE-22390 > URL: https://issues.jboss.org/browse/JBIDE-22390 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Alexey Kazakov > Assignee: George Gastaldi > Priority: Critical > Fix For: 4.4.0.Alpha2 > > > 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...]. > If Forge is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Forge by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3903) Platform Installer does not Setup Docker Env-Vars

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3903?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3903: -------------------------------------- [~tmader] we do install Docker Tools as part of devstudio. Docker Tools == Eclipse plugins which support Docker. But Docker Tools assume you have Docker itself (CLI stuff) installed and configured. +1 to improve the error message in Docker Tools. This should be reported upstream (to Docker Tools) in eclipse bugzilla. [~xcoulon] please help Thomas with that. > Platform Installer does not Setup Docker Env-Vars > ------------------------------------------------- > > Key: JBDS-3903 > URL: https://issues.jboss.org/browse/JBDS-3903 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: docker, platform-installer > Affects Versions: 10.0.0.Alpha1 > Environment: Windows > Reporter: Thomas Mäder > Assignee: Denis Golovin > > I have installed CDK, etc. from the "all in one" installer. Later, I tried to use Docker tooling. I opened the view "Docker Explorer". There was no connection shown. I tried to add a new one, but the system did not detect my default connection. > Later, I ran "Docker Quickstart Terminal" from the start menu. Now the "New Connection" dialog in docker explorer picked up the default connection. > As a user, I have no indication that I have to run the docker terminal in order to use the docker tooling in eclipse. If there are environment variables to be set up, the installer should do so. It is the reasonable expectation on Windows. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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 May 2016