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 "Corona HowTo: Include a New Plugin in Build"
(→Create a News Corona Plugin) |
(→Modify Build) |
||
| Line 1: | Line 1: | ||
| + | |||
| + | =Plugin Structure= | ||
| + | A Corona plugin is a regular Equinox plugin/fragment that conforms to Europa build practices. If a new plugin is created the following should be assured: | ||
| + | * 4-part version numbering should be used, the first three parts are numbers, the last is "qualifier" word, for example: 0.5.0.qualifier | ||
| + | * plugin must correctly list its required JVM versions in the manifest/plugin.xml | ||
| + | * build.properties file must list all files that should be included in the build result (the option bin.includes) | ||
=Modify Build= | =Modify Build= | ||
| + | The following steps should be taken to include a new plugin in build: | ||
| + | * add the plugin to Corona Client and/or Server feature (steps for adding to Corona client feature) | ||
| + | ** open org.eclipse.corona.client | ||
| + | ** open feature.xml | ||
| + | ** on Plug-ins and fragments tab select Add and select the new plugin | ||
| + | ** then select Versions and select Synchronization options: "Copy versions from plug-in and fragment manifests" | ||
| + | ** save the feature.xml and commit to CVS | ||
| + | * modify Corona maps for Corona client and/or server | ||
| + | ** the maps can be found in maps folder in CVS under org.eclipse.corona | ||
| + | ** add a line that represents the plugin, the line must specify plugin/fragment, name and CVS access parameters analogously to other defined entries in maps. | ||
| + | |||
| + | =Check if the Automated build works= | ||
Revision as of 11:20, 18 December 2006
Plugin Structure
A Corona plugin is a regular Equinox plugin/fragment that conforms to Europa build practices. If a new plugin is created the following should be assured:
- 4-part version numbering should be used, the first three parts are numbers, the last is "qualifier" word, for example: 0.5.0.qualifier
- plugin must correctly list its required JVM versions in the manifest/plugin.xml
- build.properties file must list all files that should be included in the build result (the option bin.includes)
Modify Build
The following steps should be taken to include a new plugin in build:
- add the plugin to Corona Client and/or Server feature (steps for adding to Corona client feature)
- open org.eclipse.corona.client
- open feature.xml
- on Plug-ins and fragments tab select Add and select the new plugin
- then select Versions and select Synchronization options: "Copy versions from plug-in and fragment manifests"
- save the feature.xml and commit to CVS
- modify Corona maps for Corona client and/or server
- the maps can be found in maps folder in CVS under org.eclipse.corona
- add a line that represents the plugin, the line must specify plugin/fragment, name and CVS access parameters analogously to other defined entries in maps.