Re: [p2-dev] p2 headless and rcp feature

[Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx>]

Could you detail how the org.eclipse.equinox.p2.user.ui.feature.group does not suit the need of an RCP application?
I think the steps proposed by Andrew are here to palliate the fact that the product editor does not allow for a mixed mode of feature and plugin or at least the import of plug-ins from a feature already defined when used in plugin mode.

Chris Aniszczyk ---03/09/2009 12:23:19 PM---Howdy p2 team, Have we considered adding a "rcp" feature? I know there has been some

From:	Chris Aniszczyk <zx@xxxxxxxxxxxxxxxxx>
To:	p2-dev@xxxxxxxxxxx
Date:	03/09/2009 12:23 PM
Subject:	[p2-dev] p2 headless and rcp feature

---

Howdy p2 team,

Have we considered adding a "rcp" feature? I know there has been some discussion of a headless/core feature in this bug:
    https://bugs.eclipse.org/bugs/show_bug.cgi?id=262332

The reason I ask is because we don't have a good story to tell people right now if they want to add "update" functionality to their RCP applications. This is also evident by Andrew's blog post (http://aniefer.blogspot.com/2008/06/example-headless-build-for-rcp-product.html)... it would be much easier to say "Add this p2 RCP feature" to your product than add these plug-ins and hit "Add Required Plug-ins".

Note that we had this same problem in the past with Update. I believe update.configurator only shipped with the RCP feature and if you needed Update functionality, you would add update.core/ui and that's it. This is more complicated with p2 now and having something like a feature would really make things easier.

Anyone else have comments on this issue and how we effect our downstream adopters?

Cheers,

-- 
Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
http://twitter.com/eclipsesource | http://twitter.com/caniszczyk_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev