<br><br><div><span class="gmail_quote">On 9/2/06, <b class="gmail_sendername">Max Rydahl Andersen</b> <<a href="mailto:max.andersen@jboss.com">max.andersen@jboss.com</a>> wrote:</span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>ok, so just so i understand "make the dependencies it generates...be<br>features" means<br>that you copy an existing complete feature as-is, instead of taking<br>individual parts<br>or create a new feature, correct?
</blockquote><div><br>Right.. this means we copy everything under the features/xxx directory into the features directory of the current builder. Nothing new is created..<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> 1) If a plugin is listed as a <plugin>, it gets auto-bundled just like in<br>> standard PDE build (no change). Anything here will be seen in both<br>> "bundle" and "nodeps" downloads.<br>
<br>+1 (if "bundle" means the type of downloads we provide now for each<br>plugin? not bundle as in full eclipse SDK + deps + our plugin)</blockquote><div><br>Yes, bundle here means "plugins + dependencies" not our "Bundle" which includes everything =)
<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Would be cool if one could automatically run through<br>plugin.xml/feature.xml and look for "evil" plugin references.
</blockquote><div><br>I have absolutely no idea what you mean by "evil" ... care to expand a bit more? (I'm guessing you mean org.eclipse.emf.*? =)<br></div><br></div><br>-- <br>Marshall Culpepper<br><a href="mailto:marshall.culpepper@jboss.com">
marshall.culpepper@jboss.com</a><br>JBoss Eclipse IDE Lead<br>JBoss, a division of Red Hat