[jbosstools-issues] [JBoss JIRA] (JBIDE-16375) Allow to extend Central extensions catalog with "Early Access" stuff

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-16375:
------------------------------------

Simpler... 

* since EA content is only released at intervals (eg., once a milestone) and 
* rarely will EA content magically evolve from EA status to non-EA outside of a JBDS release, and
* it's unlikely that new EA content will suddenly need to be added into Central outside of a release (I know of ONE exception to this since we started having a Central: JBIDE-17002)

Why not just label the EA connectors [0] in the existing JBDS or JBT central discovery plugins with a particular certificationId [1], and let the UI handle sorting/filtering it?

[0] https://github.com/jbosstools/jbosstools-discovery/blob/master/jbdevstudio/com.jboss.jbds.central.discovery/plugin.xml#L256
[1] https://github.com/jbosstools/jbosstools-discovery/blob/master/jbdevstudio/com.jboss.jbds.central.discovery/plugin.xml#L34 

Why do we need to put a SECOND plugin into the directory.xml file? How often do you expect EA content in Central to change?

If you look in the code above, you'll see that we already DO this in JBDS 7/8 Central for VJET and in JBT 4.1/4.2 Central for Arquillian & VJET. Why introduce a whole other set of jobs, plugins, publishing process, etc. for something that (unless I'm woefully mistaken) need not be so segregated?

What's the value add in making it separate, when the jobs today for rebuilding Central Discovery are so fast and easy to use?
                
> Allow to extend Central extensions catalog with "Early Access" stuff
> --------------------------------------------------------------------
>
>                 Key: JBIDE-16375
>                 URL: https://issues.jboss.org/browse/JBIDE-16375
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: central, discovery
>            Reporter: Mickael Istria
>            Assignee: Mickael Istria
>             Fix For: 4.2.0.Beta2
>
>
> In order to make it easier for people to consume some "Beta" extensions from JBT or JBDS release (such as installing a Beta of JBT-IS on top of a JBT release), it would make sense to have Central allow users to select some catalogs in a UI entry such as "Include Experimental stuff" to show additional catalog entries.
> Either this could be a single catalog with the experimental content being annotated, or it could be 2 (or more catalogs) which have different quality levels.
> The Central UI will need to give feedback on the quality level for a given entry ("supported" or "experimental" or ...).

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