[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=12931692#comment-12931692 ] 

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

[~nickboldt] i'm not following what you mean with your last comment. 

[~mmusaji] other examples than completely new things (like arquillian) is early versions of plugins that are being developed. i.e. SOA tooling were not ready for 7.0/7.1 but they did have an beta updatesite - could we find a way to make this more easily available to our users rather than having to manually install from external updatesite.

Another combination is making beta/alpha versions of a JBDS release train(like 7.1.1 in 7.x) available as an update to use from within Central.

The above have in discussions said it needs different or additional UI and some clear handling of users being made aware they are running a non-supported combination.
 
                
> 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