|Re: Buckminster not picking up target platform? [message #652452 is a reply to message #652449]
||Thu, 03 February 2011 23:56
| Henrik Lindberg
Registered: July 2009
When building a product you must make sure that everything that is |
required is available by the director (so it can be included in the
product it is "installing for the purpose of zipping it up"). The fact
that you have them in your TP does not make them availabl to the
director, or included in your product.
As contrast, if you run your bundles installed in the IDE, the "TP"
stuff is expected to be installed in your IDE.
You can either include all required bundles directly in your product
feature (or some other feature included in the product feature, if you
want to separate them), or modify how the directory creates the product.
If you do not want to include them in your feature, the call to the
directory must be altered to include additional p2 sites (that do have
the required things). This way, your p2 site will not include them, and
people updating your product that wants to update the bundles "in your
tp" need to also have a reference to the p2 update site that has them.
I hope that makes it clearer.
On 2/4/11 12:43 AM, Josh Hester wrote:
> So I'm trying to use buckminster to build our osgi bundles. The p2.site
> target works fine and I'm able to build all of my bundles.
> The problem comes when I try to install the product. Buckminster starts
> telling me it can't find bundles that are included in my target
> platform. What do I need to do to get Buckminster to look at the target
> platform? Is there some non documented magic here?
> I'm under the impression that I just need to include my bundles in a
> feature and that 3rd party bundles only need to be in my target
> platform, is this correct?
Powered by FUDForum
. Page generated in 0.02333 seconds