[jbosstools-issues] [JBoss JIRA] (JBDS-2168) Review and improve mechanism to provide 3rd-party features

Mickael Istria (JIRA) jira-events at lists.jboss.org
Wed May 30 06:19:18 EDT 2012


     [ https://issues.jboss.org/browse/JBDS-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mickael Istria reassigned JBDS-2168:
------------------------------------

    Assignee: Max Rydahl Andersen  (was: Mickael Istria)


We need to make a choice on this:
* Do we directly provide 3rd-party features?
* Do we wrap them in a "require" way to provide our own grain and label in UI, but let people install other versions from external sites?
* Do we wrap them im an "include" way to provide our own grain and label in UI, but force people to use the version we decide for each feature and force them to update 3rd-party features only via provisioning?
                
> 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: Max Rydahl Andersen
>             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

        


More information about the jbosstools-issues mailing list