<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 01/10/2013 07:21 PM, Rob Cernich
wrote:<br>
</div>
<blockquote
cite="mid:1998072584.4410374.1357842114020.JavaMail.root@redhat.com"
type="cite">
<style type="text/css">p { margin: 0; }</style>
<div style="font-family: times new roman,new york,times,serif;
font-size: 12pt; color: #000000">Yep. That's what I was
thinking. As I said, I'm not sure about the upgrade process.
My concern is that once one of the child features is installed,
you may not be able to update at all (i.e. a wtp upgrade would
balk because the e42 plugin isn't compatible). That said, users
probably won't be using the update mechanism when updating the
platform, so you should be good.<br>
</div>
</blockquote>
I see a tricky use-case.<br>
From definition of optional feature: "Some included features may be
useful add-ons, but are not vital to the proper
functioning of the overall product. Feature providers can elect to
mark them as <b>optional</b>.
Optional features will only be installed if all their required
features and plug-ins are
available. If not installed right away, optional features can be
added at a later date."<br>
A user that had Kepler but not Dali installed will have none of
those optional features installed. He'll need to install Dali
manually. I don't think users will like to dig for dependencies to
be able to install a feature, it's so pre-p2 !<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>