[
https://issues.jboss.org/browse/JBDS-2168?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-2168:
----------------------------------
Spring & Mylyn are examples of where the 3rd party feature(s) provide more than we
want to include; thus, we either wrap their plugins (mylyn) or a subset of their features
(Spring) to restrict what the customer gets on installation.
IMHO, this is a better approach than just saying "go install it yourself" or
pointing at the 3rd party site directly.
If we're going to take the time to provide our own mirror of the bits (for the
purposes of controlling what appears in Central and on Extras), why not take the extra
branding/control step and wrap w/ features too?
Review and improve mechanism to provide 3rd-party features
----------------------------------------------------------
Key: JBDS-2168
URL:
https://issues.jboss.org/browse/JBDS-2168
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Security Level: Public(Everyone can see)
Components: 3rdPartyDependencies, Build
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 6.x
Currently, we wrap (in a 1-1 mapping) most 3rd-party features as "requirements"
into features of ours. It allows to show our license and lable when installing.
We should think about other approaches, and choose the best one:
* Get rid of our features and directly include 3rd-party features in site. Keep our
features only when we want an assembly of several 3rd-party features (we do it for
springide)
* Prefer inclusion over requirement so that we can restrict the version we allow for
3rd-party features. If someone wants a different one, he'll have to uninstall the JBDS
"supported" feature first.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira