[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [buckminster-dev] Help needed in understandig of buckminster + director
|
Hi,
the repository created when using the site.p2 action in Buckminster
contains the bundles that are *included* by the features in your
product. Bundles from your TP need to come from a different repository
like Helios.
How you organize this depends on how you want users to later update the
procuct - i.e if your repo contains all bundles, or if users need to
also contact the eclipse standard repository.
If all you want to do is to create a product zip, you can do that by
adding the additional repository URLs to the call to the director.
Please note that this list : buckminster-dev is for development of
Buckminster itself. Please use the eclipse.tools.buckminster
list/newsgroup/forum for all other discussions.
Regards
- henrik
On 9/23/10 3:14 PM, Thomas Grigat wrote:
Hi,
I decided to try out buckminster for bulding an eclipse product and ran
into some issues while trying to build an update site for my eclipse
project and building the product from that using the director tool.
Building the update site out of eclilpse works. But when i tell director
to install the product i get anoying errors telling me that plug in wich
is referenced by one of my plugins hat a missing dependency.
I thought buckminster would find all dependeceies (from plugin.xml,
feature.xml) from the defined target platform, that contains all needed
plugin, and materializes them for the updatesite but that insnt so.
Exporting product from eclipse wizard works...
What am I doing wrong ?
