On 03/20/2012 11:33 AM, Max Rydahl Andersen wrote: 

      

        
I'll make the necessary changes in affected component to replace inclusion by dependency.
If you see any trouble because of this, please tell me; it will be ok to use inclusion if required, and a workaround exist to get sources for such features too.


      

      
either open a jira for these modules with a patch or send the fisheye changeset here when done so its easy to look at.

The only reason I recall there being  a need for feature inclusion is when the updatesite zip is created - then it will contain the proper dependencies.

    

    Indeed, included features are a way to solve the issue you describe.
    

    However, the clean way to modify update-sites is to add the feature
    (even if it is not categorized) to the site.xml or category.xml
    directly. As Denis explained, including features is OK if you (as a
    project/component) are the only one building and shipping the
    included features.

    

    
-- 

      Mickael Istria

      Eclipse developer at JBoss,
        by Red Hat

      My blog - My Tweets