You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@wookie.apache.org by "Scott Wilson (JIRA)" <ji...@apache.org> on 2014/02/02 22:24:09 UTC

[jira] [Updated] (WOOKIE-226) Enable dependencies for features

     [ https://issues.apache.org/jira/browse/WOOKIE-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Scott Wilson updated WOOKIE-226:
--------------------------------

    Fix Version/s:     (was: 1.0.0)
                   2.0.0

> Enable dependencies for features
> --------------------------------
>
>                 Key: WOOKIE-226
>                 URL: https://issues.apache.org/jira/browse/WOOKIE-226
>             Project: Wookie
>          Issue Type: Sub-task
>          Components: Feature Management
>            Reporter: Scott Wilson
>            Priority: Minor
>             Fix For: 2.0.0
>
>
> Some features depend on others; at the moment we rely on widget authors to declare all features needed by a widget explicitly, or to bundle dependent scripts in each feature. This can cause problems where several features depend on the same scripts - for example several features use JQuery and it would make more sense to have a single "JQuery Feature" that these depended on, that could be loaded by the server as required.
> This could be done by adding a <dependency> element to the feature.xml, rather similar to in Shindig, that is used when processing server features.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)