| Re: [p2-dev] tooling installable units |
Hi, Some of them are auto-generated, e.g. during product publishing. Two examples: - tooling.osgi.bundle.default configuration unit (CU) to apply default instructions for installation and setting start level of bundles in the repository - each .product file may contain a configurations section with the start-up settings for particular bundles, included in it (whether the bundle is marked for start and at what start level). For every such bundle, a tooling.* CU is generated. I bet that this is the majority of CUs you have encountered so far. J (Btw, the “tooling” prefix can be changed with the “-flavor” option of the product publisher application) In general, the tooling CUs are usually defined as fragments to certain installable units in the p2 repository to customize the process of their provisioning to systems, most often by overriding or attaching new touchpoint instructions for execution. Kind regards, Shenol Yousouf SAP Labs Bulgaria From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Paul Webster On Sun, Dec 11, 2011 at 9:34 AM, Igor Fedorenko <ifedorenko@xxxxxxxxxxxx> wrote: What are the usecases behind tooling.* installable units found in most
|