[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....
]
Nick Boldt commented on JBDS-2168:
----------------------------------
Require: won't be on the resulting update site
Include: WILL be on the resulting update site
As there is no other place to provide the features for a JBDS user (because we don't
want them getting the bits from eclipse.org or jboss.org, but only the site on
devstudio.jboss.com), they need to be INCLUDED.
If the dependency exists on the target platform, then it can be simply REQUIRED.
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