[
https://issues.jboss.org/browse/JBIDE-17808?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-17808:
----------------------------------------
Yes, it's because at that time, we didn't figure out that using certification id
would do the trick.
Now, if it comes to comparing an installation with the set of supported artifacts, since
the set of supported artifacts isn't set in stone and is subject to change
independently of what user install/uninstall, I have the feeling that we'll indeed
need a remote reference of what's supported, just like it seemed necessary at the
beginning, before we started relying on certificationId.
However, the list of supported plugins is actually already there: it's the content of
main JBDS site + Discovery (non Early Access) site. So this issue just becomes a
comparison between an installation, and the content of remote sites.
Identify which installed IUs are from Early Access vs.
supported/tested versions
--------------------------------------------------------------------------------
Key: JBIDE-17808
URL:
https://issues.jboss.org/browse/JBIDE-17808
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: central
Reporter: Nick Boldt
Fix For: 4.2.0.Beta3
[~maxandersen] brought up a good point on a call today:
we have no way from within JBDS of identifying which installed IUs were installed from
Early Access vs. those what were installed from Central or another "supported"
location.
Thus we need some sort of UI to list installed IUs that are "Early Access".
This could be... (brainstorming now):
* a text file with the list of things installed from Early Access (features and plugins)
* a set of asterisks added to the Help > About dialogs when browsing for installed
features / plugins
* a way to filter the plugin view (Help > About) to show only EA content (or exclude
it)
* ... ?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)