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 "Developer's guide to adding new plugins to the AJDT release"
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
==Adding source plugins that contain tests only (not for distribution)== | ==Adding source plugins that contain tests only (not for distribution)== | ||
| − | + | For a new test plugin: | |
#Check the test plugin into CVS (See the [http://www.eclipse.org/ajdt/developers.php#q:cvs developer's guide] for more information on CVS. | #Check the test plugin into CVS (See the [http://www.eclipse.org/ajdt/developers.php#q:cvs developer's guide] for more information on CVS. | ||
#Add test plugin to the feature ''org.eclipse.aspectj.feature_tests'' | #Add test plugin to the feature ''org.eclipse.aspectj.feature_tests'' | ||
| − | #Ensure that it is "unpacked" ( | + | #Ensure that it is "unpacked" (specify in ''org.eclipse.aspectj.feature_tests/feature.xml'') |
| − | #Ensure a test.xml is in the plugin | + | #Ensure a test.xml is in the plugin. Copy from another test plugin and change paths appropriately. Ensure to appropriately choose either ui-test or core-test |
#JUnit 4 is not supported by eclipse testing framework (org.eclipse.test). {{bug|153429}} tracks this. | #JUnit 4 is not supported by eclipse testing framework (org.eclipse.test). {{bug|153429}} tracks this. | ||
| − | + | #Edit the build.properties file for the new test plugin and ensure that it contains the test.xml and all other files required for the binary build. The .class files should be in their own jar. Can copy from other build.properties files. | |
| − | #Edit the build.properties file and ensure that it contains the test.xml and all other files required for the binary build. The .class files should be in their own jar. Can copy from other build.properties files. | + | #Edit MANIFEST.MF and add the new jar for the class files (specified in build.properties) to the classpath. |
| − | #Edit MANIFEST.MF and add the new jar (specified in build.properties) to the classpath. | + | #Update the copy-sources target in customTargets.xml ant script in org.eclipse.ajdt.releng project. |
| + | #Update the run-test-eclipse, copy-test-results, and check-results targets in the buildAll.xml file. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| + | [http://www.eclipse.org/articles/Article-PDE-Automation/automation.html This article] describes the headless testing process. | ||
| − | + | ==Adding source plugins that are meant for distribution== | |
| − | + | A lot of similarity to above, but some differences: | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | #Add plugin to appropriate feature (probably org.eclipse.ajdt-feature). This plugin should probably be "packed". | |
| + | #Update the copy-sources target in customTargets.xml ant script in org.eclipse.ajdt.releng project. | ||
| − | |||
| + | That's probably it. | ||
==Adding third party binary plugins for distribution== | ==Adding third party binary plugins for distribution== | ||
| − | AJDT | + | AJDT includes Equinox Aspects in its distribution. Equinox Weaving is grabbed from the Equinox/RT's CVS repository using a map file specified in org.eclipse.ajdt.releng/maps. If it is necessary to include more 3rd party plugins, then follow the same steps as is used for Equinox Weaving. Be sure to choose a stable tag from the source repository. Also, be sure to file a CQ for the new plugins. |
| − | + | ||
[[Category:AJDT]] | [[Category:AJDT]] | ||
Latest revision as of 10:09, 17 March 2010
Adding source plugins that contain tests only (not for distribution)
For a new test plugin:
- Check the test plugin into CVS (See the developer's guide for more information on CVS.
- Add test plugin to the feature org.eclipse.aspectj.feature_tests
- Ensure that it is "unpacked" (specify in org.eclipse.aspectj.feature_tests/feature.xml)
- Ensure a test.xml is in the plugin. Copy from another test plugin and change paths appropriately. Ensure to appropriately choose either ui-test or core-test
- JUnit 4 is not supported by eclipse testing framework (org.eclipse.test). bug 153429 tracks this.
- Edit the build.properties file for the new test plugin and ensure that it contains the test.xml and all other files required for the binary build. The .class files should be in their own jar. Can copy from other build.properties files.
- Edit MANIFEST.MF and add the new jar for the class files (specified in build.properties) to the classpath.
- Update the copy-sources target in customTargets.xml ant script in org.eclipse.ajdt.releng project.
- Update the run-test-eclipse, copy-test-results, and check-results targets in the buildAll.xml file.
This article describes the headless testing process.
Adding source plugins that are meant for distribution
A lot of similarity to above, but some differences:
- Add plugin to appropriate feature (probably org.eclipse.ajdt-feature). This plugin should probably be "packed".
- Update the copy-sources target in customTargets.xml ant script in org.eclipse.ajdt.releng project.
That's probably it.
Adding third party binary plugins for distribution
AJDT includes Equinox Aspects in its distribution. Equinox Weaving is grabbed from the Equinox/RT's CVS repository using a map file specified in org.eclipse.ajdt.releng/maps. If it is necessary to include more 3rd party plugins, then follow the same steps as is used for Equinox Weaving. Be sure to choose a stable tag from the source repository. Also, be sure to file a CQ for the new plugins.