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 "EDT:How to add new EDT plugins"
m |
|||
| Line 1: | Line 1: | ||
| − | When a new plugin is added to EDT, the release engineer should do the following. | + | When a new plugin is added to EDT, the release engineer should do the following. |
| − | * Add the plugin project to our CVS repository. (This could be done by any committer.) Do Team | + | *First, be sure the new plugin's MANIFEST.MF is correct. |
| − | * If the ''folder'' in the previous step is new, update the project metadata. | + | **The plugin ID must begin with '''org.eclipse.edt'''. |
| − | * Add the new plugin to the feature.xml of its feature. | + | **The version must be of the form '''0.7.0.qualifier''' (use the correct numbers for the release you're developing). |
| − | * Make an entry in the map file (org.eclipse.edt.releng/maps/edt.map) for the new plugin. | + | **The provider must be '''Eclipse EGL Development Tools'''. |
| − | * Do Team | + | **Choose your dependencies carefully. |
| + | ***Don't require a particular version of a non-EDT plugin without good reason. | ||
| + | ***Be aware that the build may be done with an older version of Eclipse than you are using. For example, EDT 0.7.0 is built on Eclipse 3.6.0, even though the latest version of Eclipse 3.6 is 3.6.2. We do this so EDT will work on every Eclipse 3.6.x release. | ||
| + | *Add the plugin project to our CVS repository. (This could be done by any committer.) Do Team > Share Project > CVS and choose :extssh:you@dev.eclipse.org:/cvsroot/tools. Choose Use Specified Module Name and enter org.eclipse.edt/''folder''/''pluginName''. | ||
| + | *If the ''folder'' in the previous step is new, update the project metadata. Go to https://dev.eclipse.org/portal/myfoundation/portal/portal.php, click view next to tools.edt, and click maintain next to Project Info Meta-data. Click edit and update the list under "source repository". | ||
| + | *Add the new plugin to the feature.xml of its feature. | ||
| + | *Make an entry in the map file (org.eclipse.edt.releng/maps/edt.map) for the new plugin. | ||
| + | *Do Team > Release to get the code into the next build. | ||
[[Category:EDT]] | [[Category:EDT]] | ||
Revision as of 15:32, 19 August 2011
When a new plugin is added to EDT, the release engineer should do the following.
- First, be sure the new plugin's MANIFEST.MF is correct.
- The plugin ID must begin with org.eclipse.edt.
- The version must be of the form 0.7.0.qualifier (use the correct numbers for the release you're developing).
- The provider must be Eclipse EGL Development Tools.
- Choose your dependencies carefully.
- Don't require a particular version of a non-EDT plugin without good reason.
- Be aware that the build may be done with an older version of Eclipse than you are using. For example, EDT 0.7.0 is built on Eclipse 3.6.0, even though the latest version of Eclipse 3.6 is 3.6.2. We do this so EDT will work on every Eclipse 3.6.x release.
- Add the plugin project to our CVS repository. (This could be done by any committer.) Do Team > Share Project > CVS and choose :extssh:you@dev.eclipse.org:/cvsroot/tools. Choose Use Specified Module Name and enter org.eclipse.edt/folder/pluginName.
- If the folder in the previous step is new, update the project metadata. Go to https://dev.eclipse.org/portal/myfoundation/portal/portal.php, click view next to tools.edt, and click maintain next to Project Info Meta-data. Click edit and update the list under "source repository".
- Add the new plugin to the feature.xml of its feature.
- Make an entry in the map file (org.eclipse.edt.releng/maps/edt.map) for the new plugin.
- Do Team > Release to get the code into the next build.