April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-623) Add FeedHenry Information to Existing Article about Hybrid Mobile Apps

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-623?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-623: ------------------------------- Sprint: 2015/S8 (13-Apr > 26-Apr), 11-May -> 24-May 2015-JBDS/JBT, 25-May -> 07-Jun 2015-JBDS/JBT, 08-Jun -> 21-Jun 2015-JBDS/JBT, 22-Jun >> 05-Jul 2015-JBDS/JBT, 06-Jul >> 19-Jul 2015-JBDS/JBT, 20-Jul >> 02-Aug 2015-JBDS/JBT, 03-Aug >> 16-Aug 2015-JBDS/J 2, 31-Aug >> 13-Sep 2015-JBDS/JBT, 28-Sep >> 11-Oct 2015-JBDS/JBT, 12-Oct >> 25-Oct 2015-JBDS/JBT, 26-Oct >> 08-Nov 2015-JBDS/JBT, 09-Nov >> 22-Nov 2015-JBDS/JBT, 23-Nov >> 06-Dec 2015-JBDS/JBT, 04-Jan >> 17-Jan 2016-JBDS/JBT, 18-Jan >> 31-Jan 2016-JBDS/JBT, 01-Feb >> 14-Feb 2016-JBDS/JBT, 15-Feb >> 28-Feb 2016-JBDS/JBT, 29-Feb >> 13-Mar 2016-JBDS/JBT, 14-Mar >> 27-Mar 2016-JBDS/J 2, 28-Mar >> 10-Apr 2016-JBDS/JBT, 25-Apr >> 08-May 2016-JBDS/JBT (was: 2015/S8 (13-Apr > 26-Apr), 11-May -> 24-May 2015-JBDS/JBT, 25-May -> 07-Jun 2015-JBDS/JBT, 08-Jun -> 21-Jun 2015-JBDS/JBT, 22-Jun >> 05-Jul 2015-JBDS/JBT, 06-Jul >> 19-Jul 2015-JBDS/JBT, 20-Jul >> 02-Aug 2015-JBDS/JBT, 03-Aug >> 16-Aug 2015-JBDS/J 2, 31-Aug >> 13-Sep 2015-JBDS/JBT, 28-Sep >> 11-Oct 2015-JBDS/JBT, 12-Oct >> 25-Oct 2015-JBDS/JBT, 26-Oct >> 08-Nov 2015-JBDS/JBT, 09-Nov >> 22-Nov 2015-JBDS/JBT, 23-Nov >> 06-Dec 2015-JBDS/JBT, 04-Jan >> 17-Jan 2016-JBDS/JBT, 18-Jan >> 31-Jan 2016-JBDS/JBT, 01-Feb >> 14-Feb 2016-JBDS/JBT, 15-Feb >> 28-Feb 2016-JBDS/JBT, 29-Feb >> 13-Mar 2016-JBDS/JBT, 14-Mar >> 27-Mar 2016-JBDS/J 2, 28-Mar >> 10-Apr 2016-JBDS/JBT, 11-Apr >> 24-Apr 2016-JBDS/J 2) > Add FeedHenry Information to Existing Article about Hybrid Mobile Apps > ---------------------------------------------------------------------- > > Key: TOOLSDOC-623 > URL: https://issues.jboss.org/browse/TOOLSDOC-623 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Reporter: Burr Sutter > Assignee: Supriya Bharadwaj > Fix For: 4.2.3.Final > > > Originally reported by Burr here: https://issues.jboss.org/browse/JBDS-3397 > Description: https://access.redhat.com/articles/1295913 > We should add FeedHenry to this document. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

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

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-710?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-710: ------------------------------- Sprint: 01-Feb >> 14-Feb 2016-JBDS/JBT, 15-Feb >> 28-Feb 2016-JBDS/JBT, 29-Feb >> 13-Mar 2016-JBDS/JBT, 14-Mar >> 27-Mar 2016-JBDS/J 2, 28-Mar >> 10-Apr 2016-JBDS/JBT, 25-Apr >> 08-May 2016-JBDS/JBT (was: 01-Feb >> 14-Feb 2016-JBDS/JBT, 15-Feb >> 28-Feb 2016-JBDS/JBT, 29-Feb >> 13-Mar 2016-JBDS/JBT, 14-Mar >> 27-Mar 2016-JBDS/J 2, 28-Mar >> 10-Apr 2016-JBDS/JBT, 11-Apr >> 24-Apr 2016-JBDS/J 2) > JBDS 9.1 GA: Document a use case for Hibernate Tooling > ------------------------------------------------------ > > Key: TOOLSDOC-710 > URL: https://issues.jboss.org/browse/TOOLSDOC-710 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 9.1 GA > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Labels: Hibernate-tools > Fix For: 9.1 GA > > > Draft a use case and document it for Hibernate Tools. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-718) Getting Started / Readme for new CDK users

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-718?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-718: ------------------------------------ >From Rob: The basic use case is: 1) Create a CDK server adapter, pointing to the folder with the Vagrantfile from cdk installation. If from installer, this folder should have a .cdk file 2) right-click server adapter and select 'start'. this should run vagrant up, and start the server 3) credentials chosen in new server wizard should be passed to vagrant up command via environment variables, so vagrant up should succeed 4) Once started, a new connection in Docker Explorer should be added if it didn't exist yet. 5) Once started, a new connection in OpenShift Explorer should be added if it didn't exist yet. 6) These two connections should 'work'. ie, if you expand them, the proper elements should be where they belong 7) right-click server and select 'stop' should run vagrant halt 8) repeated start / stop commands shouldn't break This may sound simple, but much of the work was focussed on the openshift repository, so the rest of the usecases all involve openshift workflows. Once you have an openshift connection, you should be able to create an application, a project, whether node.js or eap, from the templates. This should clone some remote git repo, import a project into the workspace, and begin building the app on the openshift instance. Once the app is created and built, you should be able to turn the openshift app into its own server adapter by right-clicking the openshift app and selecting "Server Adapter..." >From there you should be able to publish changes incrementally or fully via the servers view by right-clicking the openshift server. I believe Martin may have a more in-depth test plan available for both the CDK and OpenShift instances, or can help you find it. Martin? > Getting Started / Readme for new CDK users > ------------------------------------------- > > Key: TOOLSDOC-718 > URL: https://issues.jboss.org/browse/TOOLSDOC-718 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 9.1 CR1 > Reporter: Nick Boldt > Assignee: Misha Ali > Labels: Havoc > Fix For: 9.1 GA > > > See JBDS-3738. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3794) Installer - We should document the uninstall steps

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3794?page=com.atlassian.jira.plugin.... ] Alexey Kazakov resolved JBDS-3794. ---------------------------------- Resolution: Done The corresponding doc issue is resolved. Resolving this one too. > Installer - We should document the uninstall steps > -------------------------------------------------- > > Key: JBDS-3794 > URL: https://issues.jboss.org/browse/JBDS-3794 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: documentation, installer > Affects Versions: 9.1.0.CR1 > Reporter: Len DiMaggio > Assignee: Misha Ali > Labels: havoc > Fix For: 9.1.0.GA > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3748) Installer - We need to define/document the minimum hardware requirements for the installer (and packages installed by the installer)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3748?page=com.atlassian.jira.plugin.... ] Alexey Kazakov resolved JBDS-3748. ---------------------------------- Resolution: Done The corresponding doc issue is resolved. Resolving this one too. > Installer - We need to define/document the minimum hardware requirements for the installer (and packages installed by the installer) > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-3748 > URL: https://issues.jboss.org/browse/JBDS-3748 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: documentation, installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Misha Ali > Labels: havoc > Fix For: 9.1.0.GA > > > The latest information that I can find for JBDS is: > https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... > This is not adequate for the CDK, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3707) Installer - All-in-one installer creates situation where Browsersim fails

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3707?page=com.atlassian.jira.plugin.... ] Alexey Kazakov resolved JBDS-3707. ---------------------------------- Resolution: Partially Completed Documentation part is done. There is nothing we can do more. Resolving. > Installer - All-in-one installer creates situation where Browsersim fails > ------------------------------------------------------------------------- > > Key: JBDS-3707 > URL: https://issues.jboss.org/browse/JBDS-3707 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: documentation, installer > Affects Versions: 9.1.0.CR1 > Reporter: Len DiMaggio > Assignee: Alexey Kazakov > Labels: havoc > > Related to: JBDS-3676 > If a user performs an install with the all-in-one installer, the JDK installed will not permit Browsersim to be used. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3707) Installer - All-in-one installer creates situation where Browsersim fails

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3707?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3707: --------------------------------- Fix Version/s: 9.1.0.GA > Installer - All-in-one installer creates situation where Browsersim fails > ------------------------------------------------------------------------- > > Key: JBDS-3707 > URL: https://issues.jboss.org/browse/JBDS-3707 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: documentation, installer > Affects Versions: 9.1.0.CR1 > Reporter: Len DiMaggio > Assignee: Alexey Kazakov > Labels: havoc > Fix For: 9.1.0.GA > > > Related to: JBDS-3676 > If a user performs an install with the all-in-one installer, the JDK installed will not permit Browsersim to be used. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3698) Installer - We should document (rel notes) the versions of the installable components that we support

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3698?page=com.atlassian.jira.plugin.... ] Alexey Kazakov resolved JBDS-3698. ---------------------------------- Resolution: Done The corresponding doc task is resolved. Resolving this one too. > Installer - We should document (rel notes) the versions of the installable components that we support > ----------------------------------------------------------------------------------------------------- > > Key: JBDS-3698 > URL: https://issues.jboss.org/browse/JBDS-3698 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: documentation, installer > Affects Versions: 9.1.0.CR1 > Reporter: Len DiMaggio > Assignee: Misha Ali > Labels: havoc > Fix For: 9.1.0.GA > > > It's good that the installer will allow users to have/retain their own installed components, and verify that the installed versions are supported, but we should provide the users with a documented list of the ranges of supported versions. Thx! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3834) Install fail - what next?

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3834?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3834: -------------------------------------- I think this is a duplicate but don't have a link to the original issue. Anyway this is something we should take care of for the next release. > Install fail - what next? > ------------------------- > > Key: JBDS-3834 > URL: https://issues.jboss.org/browse/JBDS-3834 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.1.0.GA > Reporter: Misha Ali > Assignee: Denis Golovin > Priority: Minor > Fix For: 10.0.0.Alpha1 > > Attachments: fail_install.PNG > > > Testing the Installer a bit more and I realize this is currently tech preview but when one (or more) components fail, there is no next step for users. There is no cancel or quit button to exit the failed install, nor is there a retry for the failed component, nor any error message at all. As a user, I'd be confused about what I should do next at this stage. I think this might be worth looking into with UX for the 9.1 GA++ release. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3834) Install fail - what next?

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3834?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3834: --------------------------------- Fix Version/s: 10.0.0.Alpha1 > Install fail - what next? > ------------------------- > > Key: JBDS-3834 > URL: https://issues.jboss.org/browse/JBDS-3834 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.1.0.GA > Reporter: Misha Ali > Priority: Minor > Fix For: 10.0.0.Alpha1 > > Attachments: fail_install.PNG > > > Testing the Installer a bit more and I realize this is currently tech preview but when one (or more) components fail, there is no next step for users. There is no cancel or quit button to exit the failed install, nor is there a retry for the failed component, nor any error message at all. As a user, I'd be confused about what I should do next at this stage. I think this might be worth looking into with UX for the 9.1 GA++ release. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 April 2016