<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 03/20/2012 11:33 AM, Max Rydahl Andersen wrote:
<blockquote
cite="mid:EC290206-E11C-498F-B2F4-EBE9F081D0A3@redhat.com"
type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">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.
</pre>
</blockquote>
<pre wrap="">
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.</pre>
</blockquote>
Indeed, included features are a way to solve the issue you describe.
<br>
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.<br>
<br>
<div class="moz-signature">-- <br>
Mickael Istria<br>
Eclipse developer at <a href="http://www.jboss.org/tools">JBoss,
by Red Hat</a><br>
<a href="http://mickaelistria.wordpress.com">My blog</a> - <a
href="http://twitter.com/mickaelistria">My Tweets</a></div>
</body>
</html>