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

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBIDE-16375:
----------------------------------------

{quote}when will there ever be multiple versions of a connector ?{quote}
The use-case I had in mind which drove this was the case of JBDS-IS "latest release" and JBDS-IS "early-access". This is a way to deal with id overlap.

{quote}Why not just have "Show installed" and "Allow early access".{quote}
We could get indeed rid of the "newer version only" filter if we have no use-case for that.

{quote}when the user toggles this he should be warned about the downsides of this....AND when untoggling it the earlyaccess updatesites should be removed from his install since otherwise he risk getting them when running updates.{quote}
This kind of operation should not be part of the viewer per se, it should be somewhere else on the page. The filters here are only aimed at controlling what is displayed, not really to control the installation.
We could think about making the early access part a dedicated section in the page then, with operations such as "Enable early-access", or "Disable and uninstall early-access". They are more coarse-grained operations, so they don't really fit inside the viewer.

{quote}When enabling early access - the other connectors which id overlap should just not be there. i.e. it does not make sense to allow the user to install both of these and he already said "enable early access".{quote}
That's the purpose of the "Show only most recent version" filter.
It can make sense to a user to see both simultaneously, and compare their descriptions in order to decide which one fits the best his needs.

{quote}The questionn about color and indicators I would get our UX person involved with once we got the above figured out. I don't think marking the whole connector yellow helps much.{quote}
Sure.

{quote}Once earlyaccess is enabled Central itself on the first page should look different too somehow so it is clear it is not a "normal install"{quote}
Enabled on Central doesn't make the install abnormal. Having something Early-Access installed makes it so.
I'd be glad if you could suggest a concrete UI change there.

{quote} to reproduce your video which catalog should I use ? how to run it since by default it just uses the default catalog without any earlyaccess work ?{quote}
Take the jbosstools-discovery on my GitHub repo, branch JBIDE-16375-sandbox, and then build it with "mvn clean verify".
Then create a directory.xml file as described in previous comment, which reference local jars.
And then, tweak your lauch configuration to reference this catalog: add "-Djboss.discovery.directory.url=file:/path/to/directory.xml"
                
> 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