Everything is possible with p2 :) In the early days, we explored exposing extension and extension points as capabilities, however the bulk approach did not bring much and was loading the metadata with noise. Instead we decided that if ppl wanted to have extension and extension points exposed it was probably something very selective and they could use p2.inf to expose those. As for declarative service, a similar automation could be done, but we also have to account for services that are registered with code, with blueprint, etc in order to have a complete picture.
Another thing that is not clear is whether an extension or an extension point should become a capability or a requirements. Finally on the specifics of your example, this would only work if there was no platform specific configuration in your application and if everything was defined in the plugin containing the app declaration. For example it could probably work for simple things like low level apps, but not work for the sdk since a lot of additional IUs get generated from the information found in the product file. On 2011-03-06, at 9:23 AM, Gunnar Wagenknecht wrote: > Hi p2 developers, > > I'm wondering if it's possible to expose/publish extensions defined in > plugin.xml as IU capabilities? I also wonder if that is possible (or > happens already) for declarative service information? > > The use case I have in mind is "hey p2, install me everything I need for > running application org.myapp.id". The application is an IApplication. > Is there a bug open already? > > -Gunnar > > > -- > Gunnar Wagenknecht > [email protected] > http://wagenknecht.org/ > > _______________________________________________ > p2-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/p2-dev _______________________________________________ p2-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/p2-dev
