September 2013 - jbosstools-issues

[JBoss JIRA] (JBDS-2745) Support installation of Early Access / Experimental / Incubating plugins

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2745?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2745: -------------------------------------- Target Release: 8.0.0.GA (was: 7.1.0.GA) > Support installation of Early Access / Experimental / Incubating plugins > ------------------------------------------------------------------------ > > Key: JBDS-2745 > URL: https://issues.jboss.org/browse/JBDS-2745 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Central > Affects Versions: 7.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Burr Sutter > > It's been suggested that it would be nice to have Central available to install non-GA content. How might this appear? > [~burrsutter], [~maxandersen], are we talking about: > * an additional dialog warning users about untested content? (that might be ignored / blindclicked) > * an additional tab in Central for this type of content (what label would you use?) > * relabelling the content's feature descriptions / titles / copyright / license terms to be clear it's unstable content? (might be ignored) > * some other workflow? > See also JBDS-2068. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2745) Support installation of Early Access / Experimental / Incubating plugins

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2745?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2745: ------------------------------------------- I've updated the jira to be a feature request since bugs just gets automatic PM approval. With respect to the issue the main problems with these "Experimental" parts are two-fold: 1) Avoid users and support getting confused about what to install/what they have installed. 2) How to avoid earlyaccess bits conflicts with users installation (i.e. new version of a plugin that requires Luna is *not* something that you would like to install and suddenly see some of your essential plugins stop working) #1 we've currently solved by generally not introducing any earlyaccess/beta functionallity via central - there is a big value in being able to say: 'If you installed something via JBoss Central and haven't added any site other than devstudio.jboss.com/updates to your updatesites you are running supported software' (it is simple, understandable and possible to check by users and support) #2 never arises since a) we require the connectors to run on same target platform b) we don't serve updates this way, its all additions (i.e. we don't provide both a egit 2.3 and egit 3.0 plugin from central) My thinking (and i'm not sure its enough) is that we introduce the notion of a certified notion called "earlyaccess" on central connectors (like we have supported, tested, etc.). These connectors should then be shown visually "different", i.e. a yellow/black "Early Access" marker, or yellow tainted background. It depends a bit on how it is shown in central. I would *not* vote for adding an additional tab to Central - it should not get that much space. More like a checkbox in the software/update page which enables/disables "Early access allowed". When users install from this "earlyaccess" category, they should be explicitly warned - you are about to do something non-supported. With that in place users won't by "accident" install earlyaccess via central - they would always have to do something manually. The above covers the installation path, but how about when users have installed a feature - how do we/the user know if they run a supported or non-supported set of features ? Today we can detect if a user have a connector installed or not. We could use this same mechanism to detect if users installed earlyaccess features and then maybe show that someway in central (put a "Experimental" label on the central logo?) Unfortunately this wouldn't be enough since users could install parts manually via updatesite zips, dropins etc. and one version of a feature might be supported where as another one is not. Thus the idea of "blessed features/plugins" came about. Have some representation of plugins/features incl. version ranges we are ok with (supported) and which we consider (earlyaccess). This list would be stored in the discovery plugin (assuming we can make it small enough) Then central could crosscheck this list of plugins/features with what is actually running inside eclipse and mark/highlight wether there are earlyaccess parts PLUS it could report on "foreign" parts which we had no explicit knowledge/info on. To summarize my idea would be: A) add "earlyaccess" notion to connectors on central B) have explicit list of plugins/features that are considered supported vs earlyaccess C) add visual hints and UI to make it clear you installed some of this and you can figure out what you've installed that are experimental. For a full solution we should definitely also add "uninstall" support to central to allow users to remove/rollback experimental parts. > Support installation of Early Access / Experimental / Incubating plugins > ------------------------------------------------------------------------ > > Key: JBDS-2745 > URL: https://issues.jboss.org/browse/JBDS-2745 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Central > Affects Versions: 7.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Burr Sutter > > It's been suggested that it would be nice to have Central available to install non-GA content. How might this appear? > [~burrsutter], [~maxandersen], are we talking about: > * an additional dialog warning users about untested content? (that might be ignored / blindclicked) > * an additional tab in Central for this type of content (what label would you use?) > * relabelling the content's feature descriptions / titles / copyright / license terms to be clear it's unstable content? (might be ignored) > * some other workflow? > See also JBDS-2068. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2745) Support installation of Early Access / Experimental / Incubating plugins

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2745?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2745: -------------------------------------- CDW pm_ack: ? (was: +) > Support installation of Early Access / Experimental / Incubating plugins > ------------------------------------------------------------------------ > > Key: JBDS-2745 > URL: https://issues.jboss.org/browse/JBDS-2745 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Central > Affects Versions: 7.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Burr Sutter > > It's been suggested that it would be nice to have Central available to install non-GA content. How might this appear? > [~burrsutter], [~maxandersen], are we talking about: > * an additional dialog warning users about untested content? (that might be ignored / blindclicked) > * an additional tab in Central for this type of content (what label would you use?) > * relabelling the content's feature descriptions / titles / copyright / license terms to be clear it's unstable content? (might be ignored) > * some other workflow? > See also JBDS-2068. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2745) Support installation of Early Access / Experimental / Incubating plugins

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2745?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2745: -------------------------------------- Summary: Support installation of Early Access / Experimental / Incubating plugins (was: Should Central support installation of Early Access / Experimental / Incubating content?) > Support installation of Early Access / Experimental / Incubating plugins > ------------------------------------------------------------------------ > > Key: JBDS-2745 > URL: https://issues.jboss.org/browse/JBDS-2745 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Central > Affects Versions: 7.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Burr Sutter > > It's been suggested that it would be nice to have Central available to install non-GA content. How might this appear? > [~burrsutter], [~maxandersen], are we talking about: > * an additional dialog warning users about untested content? (that might be ignored / blindclicked) > * an additional tab in Central for this type of content (what label would you use?) > * relabelling the content's feature descriptions / titles / copyright / license terms to be clear it's unstable content? (might be ignored) > * some other workflow? > See also JBDS-2068. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2745) Support installation of Early Access / Experimental / Incubating plugins

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2745?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2745: -------------------------------------- Issue Type: Feature Request (was: Bug) > Support installation of Early Access / Experimental / Incubating plugins > ------------------------------------------------------------------------ > > Key: JBDS-2745 > URL: https://issues.jboss.org/browse/JBDS-2745 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Central > Affects Versions: 7.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Burr Sutter > > It's been suggested that it would be nice to have Central available to install non-GA content. How might this appear? > [~burrsutter], [~maxandersen], are we talking about: > * an additional dialog warning users about untested content? (that might be ignored / blindclicked) > * an additional tab in Central for this type of content (what label would you use?) > * relabelling the content's feature descriptions / titles / copyright / license terms to be clear it's unstable content? (might be ignored) > * some other workflow? > See also JBDS-2068. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-360) Review section 5 of "JBoss SOAP Web Services User Guide" documentation

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-360?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-360: ------------------------------------- Fix Version/s: 4.2.0 (was: 4.1.1) > Review section 5 of "JBoss SOAP Web Services User Guide" documentation > ---------------------------------------------------------------------- > > Key: TOOLSDOC-360 > URL: https://issues.jboss.org/browse/TOOLSDOC-360 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: User Guide - Web Services Tools > Affects Versions: 4.0.0.Final > Reporter: William Siqueira > Assignee: Michelle Murray > Fix For: 4.2.0 > > > Hi, > The documentation "JBoss SOAP Web Services User Guide" should be reviewed in some points. Sounds it is mentioning the configuration for previous JBDS/Eclipse versions. > In section "Chapter 5. JBoss Web Services and the development environment" it shows properties that can't be found or are different in JBDS 6. > Take as example the source code attachment, it's different in JBDS 6 and in screenshots it's possible to see it's for Eclipse, not exactly JBDS. > The referred documentation can be accessed in this link -> https://access.redhat.com/knowledge/docs/en-US/JBoss_Developer_Studio/6.0... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-358) Check 'install' sections as product name change will affect CSP

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-358?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-358: ------------------------------------------ Customer portal has changed. *Proc 3.1 Install with the Universal Installer* needs updating. Step 2. From the menu bar click Downloads, then from RHJB Middleware badge click 'Download Software' (add screen capture for clarity). > Check 'install' sections as product name change will affect CSP > --------------------------------------------------------------- > > Key: TOOLSDOC-358 > URL: https://issues.jboss.org/browse/TOOLSDOC-358 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Getting Started Guide, Installation Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.1 > > > Product name changing to Red Hat JBoss Developer Studio. Changes to CSP should be complete at end of June 2013. Recheck install instructions as these reference the product name labels in the CSP. Install instructions are provided in both Installation Guide and Getting Started Guide. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-382) Get all JBDS docs on the customer portal moved to RHJBDS page

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-382?page=com.atlassian.jira.plug... ] Michelle Murray resolved TOOLSDOC-382. -------------------------------------- Resolution: Done > Get all JBDS docs on the customer portal moved to RHJBDS page > ------------------------------------------------------------- > > Key: TOOLSDOC-382 > URL: https://issues.jboss.org/browse/TOOLSDOC-382 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: General documentation issues > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > > Old JBDS docs are located at: > https://access.redhat.com/site/documentation/JBoss_Developer_Studio/ > They need to appear under: > https://access.redhat.com/site/documentation/Red_Hat_JBoss_Developer_Studio/ > Steps: > 1. Request new branch for each book > 2. Fork GitHub repo for each plug-in to access docs > 2. Brew each book with product field (in publican.cfg) = Red Hat JBoss Developer Studio > 3. Push changed publican.cfg and Revision.xml for each book to plug-in GitHub repo > 3. Tag each book for Customer Portal > 4. Request redirect for each book -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-382) Get all JBDS docs on the customer portal moved to RHJBDS page

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-382?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-382: ------------------------------------------ Subtasks complete so marking JIRA as done. > Get all JBDS docs on the customer portal moved to RHJBDS page > ------------------------------------------------------------- > > Key: TOOLSDOC-382 > URL: https://issues.jboss.org/browse/TOOLSDOC-382 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: General documentation issues > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > > Old JBDS docs are located at: > https://access.redhat.com/site/documentation/JBoss_Developer_Studio/ > They need to appear under: > https://access.redhat.com/site/documentation/Red_Hat_JBoss_Developer_Studio/ > Steps: > 1. Request new branch for each book > 2. Fork GitHub repo for each plug-in to access docs > 2. Brew each book with product field (in publican.cfg) = Red Hat JBoss Developer Studio > 3. Push changed publican.cfg and Revision.xml for each book to plug-in GitHub repo > 3. Tag each book for Customer Portal > 4. Request redirect for each book -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-387) Get all JBDS 4.1 docs on the customer portal moved to RHJBDS page

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-387?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-387: ------------------------------------------ Docs live on customer portal: https://access.redhat.com/site/documentation/Red_Hat_JBoss_Developer_Studio/ Marking JIRA as done. > Get all JBDS 4.1 docs on the customer portal moved to RHJBDS page > ----------------------------------------------------------------- > > Key: TOOLSDOC-387 > URL: https://issues.jboss.org/browse/TOOLSDOC-387 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: General documentation issues > Affects Versions: 3.2.2.Final > Reporter: Michelle Murray > Assignee: Michelle Murray > Attachments: 40docs.png > > > See attached screen capture for list of docs to be moved. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 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 2013