[
https://issues.jboss.org/browse/JBDS-2274?page=com.atlassian.jira.plugin....
]
Nick Boldt closed JBDS-2274.
----------------------------
Resolution: Won't Fix
[~maxandersen] points out on dev call today that while it's true that hiding the
Extras site would encourage First Time Users to use Central instead of Help > Install
new, once you've used Central the Central update site URL gets added to your list of
Available Update Sites.
And since the Central site (Extras + Core + TP via a single composite site URL) ~= Extras
site, removing the Extras URL from the Available Update Sites only discourages the user
from installing those Extras by hand via Help > Install new THE FIRST TIME.
Closing WONTFIX as this doesn't really achieve anything.
Remove Extras site from p2.inf so JBDS OOTB does not reference the
site (and therefore users only see Central for installing 3rd party extras)
----------------------------------------------------------------------------------------------------------------------------------------------
Key: JBDS-2274
URL:
https://issues.jboss.org/browse/JBDS-2274
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, central, updatesite
Affects Versions: 6.0.0.Alpha1
Reporter: Nick Boldt
Assignee: Max Rydahl Andersen
Fix For: 6.0.0.Alpha2
Discussion has started regarding the removal of the Extras site URL from JBDS OOTB, so as
to encourage users to get their 3rd party bits via Central instead of using the old p2 UI
approach.
This would ensure:
a) a cleaner UI experience
b) controlled access to specific groupings of functionality (Central connectors) instead
of users being able to pick&choose any feature they want (and therefore get an
incomplete experience)
Note that advanced users can still add the Central site or the Extras site once again be
able to cherry-pick what they want to install. This just obfuscates it a little.
--
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