Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Equinox/p2/Reusing Platform Metadata"
(New page: This page outlines the current shape of the metadata for the "org.eclipse.platform.ide" product. This product is a subset of the Eclipse SDK. The SDK adds JDT, PDE, CVS and Help, but eve...) |
|||
| Line 46: | Line 46: | ||
|} | |} | ||
|} | |} | ||
| + | <br> | ||
| + | ==Using org.eclipse.platform.ide As-Is == | ||
| + | In general, the org.eclipse.platform.ide is not attractive for reuse in other products as it includes product specific branding and settings. However, in the special case of products (like EPP) that look the same as eclipse but change the default eclipse.product, then we could reuse org.eclipse.platform.ide directly. The epp.product file would specify a program argument <tt>-product</tt> which would override the entry in the config.ini file. | ||
| + | |||
| + | This would be done using a p2.inf file which should be placed beside the product file. The p2.inf file should also tell pde.build not to generate defaults CUs for start levels, because we will already get start levels from the platform.ide. | ||
| + | <pre> | ||
| + | epp.product | ||
| + | Program Arguments: -product epp.package.cpp | ||
| + | p2.inf | ||
| + | #tell pde.build not to generate start levels | ||
| + | org.eclipse.pde.build.append.startlevels=false | ||
| + | |||
| + | #add requirement on org.eclipse.platform.ide | ||
| + | requires.2.namespace=org.eclipse.equinox.p2.iu | ||
| + | requires.2.name=org.eclipse.platform.ide | ||
| + | requires.2.range=[3.5.0.I20090513-2000,3.5.0.I20090513-2000] | ||
| + | requires.2.greedy=true | ||
| + | </pre> | ||
Revision as of 18:25, 14 May 2009
This page outlines the current shape of the metadata for the "org.eclipse.platform.ide" product. This product is a subset of the Eclipse SDK. The SDK adds JDT, PDE, CVS and Help, but everything that requires special configuration exists in the base platform. This makes the platform ideal for general reuse.
The current RC1 metadata for org.eclipse.platform.ide looks something like this:
| IU Name | Provided Contents/Actions | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| org.eclipse.platform.ide | addRepository : add default repositories mdkir : create the dropins folder | |||||||||||||||||
| ||||||||||||||||||
Using org.eclipse.platform.ide As-Is
In general, the org.eclipse.platform.ide is not attractive for reuse in other products as it includes product specific branding and settings. However, in the special case of products (like EPP) that look the same as eclipse but change the default eclipse.product, then we could reuse org.eclipse.platform.ide directly. The epp.product file would specify a program argument -product which would override the entry in the config.ini file.
This would be done using a p2.inf file which should be placed beside the product file. The p2.inf file should also tell pde.build not to generate defaults CUs for start levels, because we will already get start levels from the platform.ide.
epp.product Program Arguments: -product epp.package.cpp p2.inf #tell pde.build not to generate start levels org.eclipse.pde.build.append.startlevels=false #add requirement on org.eclipse.platform.ide requires.2.namespace=org.eclipse.equinox.p2.iu requires.2.name=org.eclipse.platform.ide requires.2.range=[3.5.0.I20090513-2000,3.5.0.I20090513-2000] requires.2.greedy=true