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

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBIDE-16375:
---------------------------------------------

What is the value add ?
Because if/when earlyaccess needs to be removed it is just about removing one entry and when doing QE we don't need to give them a connector that has both - avoiding to mix any bad streams by accident. Also allows us to test earlyaccess connectors separately and mix them in with potential multiple streams instead of having to put it in every version. Also remember that the updatesite will be different for these earlyaccess components - and we got a nice simple rule at the moment of just one site url per discovery.xml (minor one, but still part of the automation setup)

Remember these earlyacces plugins will in most complicated case be *overlapping* connectors and I think it would be cleaner to keep the "overlapping connectors" separate.

Mind you, that doesn't mean JBDS-IS need to create a separate one as mentioned above - they just change the certification type and are fine since *all* of their discovery connectors will be earlyaccess.

How often do I expect EA content in central to change - more often than we do final releases. thats kinda the definition of earlyacces. 

The way VJET and Arquillian is done now is exactly what this approach is helping to make more explicit/simpler - vjet shouldn't be there on the central tp nor actually marked as supported but until now we had no other way to mark it/isolate it.

Also vjet and arquillian has zero overlaps with what is in the repo so it is not really the biggest problem here.

I think the argument of if/when we find something wrong with earlyaccess or simply just need to remove them because not earlyaccess anymore we can just remove one entry in the published catalog - no need for any rebuilds etc.

                
> 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