Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Orbit Source Bundles In Your Build"
(New page: Adding orbit source bundles to your build Typically source features are being generated as part of the build, find the build.properties requesting the creation of the source feature (it u...) |
|||
| (7 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | {{warning|Note: The contents of this page are retained for historical significance. Please see https://github.com/eclipse/orbit#readme for current information. }} | |
| − | Typically source features are being generated as part of the build, find the build.properties requesting the creation of the source feature (it usually appears in the build.properties of the SDK feature including your source | + | |
| − | The format of | + | ''Note:'' This has been updated to describe individual JAR'd source bundles and not the old-style expanded directory source bundles. |
| − | plugin@<pluginId>;version=<pluginVersion>.qualifier;unpack= | + | |
| + | Typically source features are being generated as part of the build. To change your build to consume Orbit source bundles, you will need to find the build.properties requesting the creation of the source feature (it usually appears in the build.properties of the SDK feature including your source feature) and append an entry for each of the source plug-in you are re-consuming from Orbit to the generate@ property. | ||
| + | The format of these entry is: | ||
| + | <pre> | ||
| + | plugin@<pluginId>;version=<pluginVersion>.qualifier;unpack=false | ||
| + | </pre> | ||
For example, the build.properties of the org.eclipse.sdk feature has now the following format | For example, the build.properties of the org.eclipse.sdk feature has now the following format | ||
| − | + | <pre> | |
| + | generate.feature@org.eclipse.platform.source = org.eclipse.platform,\ | ||
| + | plugin@javax.servlet.source;version=2.4.0.qualifier;unpack="false",\ | ||
| + | plugin@javax.servlet.jsp.source;version=2.0.0.qualifier;unpack="false" | ||
| + | </pre> | ||
| + | |||
| + | Of course, you will also need to update your [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.releng/maps/orbit.map?revision=1.34&view=markup map] files to reflect the location of the Orbit source bundles. | ||
| + | |||
| + | [[Category : Orbit]] | ||
Latest revision as of 12:41, 3 April 2023
Note: This has been updated to describe individual JAR'd source bundles and not the old-style expanded directory source bundles.
Typically source features are being generated as part of the build. To change your build to consume Orbit source bundles, you will need to find the build.properties requesting the creation of the source feature (it usually appears in the build.properties of the SDK feature including your source feature) and append an entry for each of the source plug-in you are re-consuming from Orbit to the generate@ property. The format of these entry is:
plugin@<pluginId>;version=<pluginVersion>.qualifier;unpack=false
For example, the build.properties of the org.eclipse.sdk feature has now the following format
generate.feature@org.eclipse.platform.source = org.eclipse.platform,\
plugin@javax.servlet.source;version=2.4.0.qualifier;unpack="false",\
plugin@javax.servlet.jsp.source;version=2.0.0.qualifier;unpack="false"
Of course, you will also need to update your map files to reflect the location of the Orbit source bundles.