[jbosstools-issues] [JBoss JIRA] (JBDS-2168) Review and improve mechanism to provide 3rd-party features
[
https://issues.jboss.org/browse/JBDS-2168?page=com.atlassian.jira.plugin....
]
Mickael Istria commented on JBDS-2168:
--------------------------------------
com.jboss.jbds.mylyn.feature contains a lot of stuff. How to decide what we
"include" and what we "require"?
I think we could:
* require all org.eclipse.[!mylyn] bundles, which should be provided by the platform
* Include all non-Eclpse bundles, which are not singleton, so no risk of conflict
* Inclide all com.atlassian plugins, which are the one we support into JBDS
* Include all Mylyn features, which are the one we support into JBDS.
Thoughts?
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