|Building a p2 site for a feature wants lots of extra plugins [message #672310]
||Fri, 20 May 2011 16:13
| Matthew Webber
Registered: December 2010
I'm having problems using Buckminster to build the p2 site for a feature.|
I have a feature project, and the feature.xml lists 7 plugins (all the plugins are in my target platform).
When I run the site.p2 action for the feature, it materializes the plugins listed for the feature (it correctly finds them in the target platform), but then it goes off and tries to find all the dependencies of the plugins.
I don't want that. I have a list of plugins, and all I want is for those explicitly listed plugins to be packaged up into a p2 site.
What's the best way to achieve that? It seems that Buckminster wants the dependencies to be materialized to the workspace, even though they will not end up in the resulting p2 site.
Powered by FUDForum
. Page generated in 0.02445 seconds