[
https://issues.jboss.org/browse/JBIDE-16375?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-16375:
----------------------------------------
I had a look at the API, and it appears that connectorId is unique, but it is totally
possible to get p2 metadata for the associated site to find out which version p2 will most
likely install.
However, we definitely need to go one grain finer than what's provided by discovery
APIs. Current APIs don't allow the same p2 site to contain mutliple version of a
connector and to choose one.
Do we want a SAME REPOSITORY to contain both "supported" and
"experimental" stuff, or can we say that both will always be separated ? The
second is easier as we won't need to rely much on versions and we can improve it with
the grain of discovery API.
Anyway, installing a connector just with its id sounds very weak for our use-cases
(updated, multiple versions...). I have the feeling we'll have to make p2 resolution
manually and directly use p2 to achieve that and make sure what will happen is what was
asked by user.
Allow to extend Central extensions catalog with "Beta"
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
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