[
https://issues.jboss.org/browse/JBDS-2168?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-2168:
----------------------------------
So what I'm getting from this is that the preference is to have MULTIPLE connectors on
Central for the following feature groups:
* Mylyn (no Git, no SVN)
* Mylyn for Git (includes Git so it'll be installed if not already)
* Git (no Mylyn)
* Mylyn for SVN (includes SVN so it'll be installed if not already)
* SVN (no Mylyn)
That gives everyone the options they need to install any or all of the 5 pieces they might
want.
Related note: more combinations == more com.jboss.jbds.* features we have to maintain as
mylyn requires a wrapper so it won't include extraneous stuff we don't want to
provide.
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