Hi, Some of them are auto-generated, e.g. during product publishing. Two examples:
- tooling.osgi.bundle.default<http://wiki.eclipse.org/Equinox/p2/Setting_Start_Levels> 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. ☺ (Btw, the “tooling” prefix can be changed with the “-flavor” option of the product publisher application<http://wiki.eclipse.org/Equinox/p2/Publisher#Product_Publisher>) 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: [email protected] [mailto:[email protected]] On Behalf Of Paul Webster Sent: 11 декември 2011 г. 19:08 ч. To: P2 developer discussions Subject: Re: [p2-dev] tooling installable units On Sun, Dec 11, 2011 at 9:34 AM, Igor Fedorenko <[email protected]<mailto:[email protected]>> wrote: What are the usecases behind tooling.* installable units found in most eclipse p2 repositories? Are do these IUs get created and used? Those look like the p2.inf instructions that are often included with eclipse SDK .product files. ex: http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.releng.eclipsebuilder/eclipse/buildConfigs/sdk/builder/p2.inf?revision=1.13&view=markup I'm not sure if some are auto-generated as well, or if they're just consumed from the p2.inf files as-is. Later, PW -- Paul Webster Hi floor. Make me a sammich! - GIR
_______________________________________________ p2-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/p2-dev
