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

[Max Rydahl Andersen (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-2745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931948#comment-12931948 ] 

Max Rydahl Andersen commented on JBDS-2745:
-------------------------------------------

[~nickboldt] the reason it has been said many times central should not contain non-GA is because there is no way to differentiate them (i.e. have it not show up at all by default, but then have a toggle that says "show experimental" or something) to allow easy install AND uninstall AND show when you have non GA bits installed. We have currently only *one* feature marked as experimental (VJET) and I would prefer it *not* be shown by default and expected to work - but currently we do. We should find a more sane way to do this.

[~leacu] "Tech Preview" of JBDSIS is not what we are talking about. Tech Preview has a very specific meaning and those releases tend to actually also be GA's ..just not supported yet. And this is ideas for JBDS 8 timeframe - not JBDS 7 nor JBDSIS 7 thus JBDSIS 7 GA is not going to be for this. The point is that we have now for 3 major GA's of JBDS not had a single JBDSIS release but we did have Alphas and Betas - but no way to make them more easily available. This jira is about finding a way to do this.

[~mmusaji] I'm trying to get away or at least reduce the amount of manual passing around of updatesites. 

compare these two:

For each experimental site do this:
1) Install JBDS 7
2) Goto Help > Install new software
3) Type in <url> and press enter
4) Browse the category types (which content is tied to the exact binary build - cannot be reordered/changed easily)
5) Press install
6) Restart Eclipse
7) on eclipse restart you can use the tools - no visual indication on you now running a 'beta' or non-supported config, nor any easy way to restore to a "safe point"

Thus if we have 2 (i.e. integration tooling and jboss tools experimental that is ~14 steps.)

to

1) Install JBDS 7
2) Goto JBoss Central update page
3) Check the "Include Experimental"  
4) Browse *all* our experimental features (not just i.e. integration tooling and it can be updated more easily without big rebuilds) 
5) Press Install
6) Restart Eclipse
7) On restart you use the tools  AND JBoss Central will now have a visual indication it is running Beta/Alpha software and you can see which "connectors" are in beta and you can uninstall them (instead of manual individual features)

With 2 or more experimental features these steps keeps being the same - if you don't uncheck the include experimental you will have it down to like 5 steps for installing and testing experimental/alpha/beta features.

                
> 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, requirements
>    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