Jump to: navigation, search

Developer's guide to adding new plugins to the AJDT release

Revision as of 00:10, 19 January 2009 by Andrew.eisenberg.as (Talk | contribs) (New page: ==Adding source plugins that are meant for distribution== ==Adding source plugins that contain tests only== #Check the test plugin into CVS (See the [http://www.eclipse.org/ajdt/develop...)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Adding source plugins that are meant for distribution

Adding source plugins that contain tests only

  1. Check the test plugin into CVS (See the developer's guide for more information on CVS.
  2. Add test plugin to the feature org.eclipse.aspectj.feature_tests
  3. Ensure that it is "unpacked" (check box in the plug-ins page)
  4. Ensure a test.xml is in the plugin copy from another test plugin and change paths appropriately. Ensure to select either ui-test or core-test
  5. JUnit 4 is not supported by eclipse testing framework (org.eclipse.test). bug 153429 tracks this.
  6. Update the customTargets.xml ant script in update site project (org.eclipse.aspectj.updatesite) (Note that build.xml and build-minimal.xml are no longer used and can probably be deleted, I don't even know if they still work. Certainly, the build.xml scripts in the individual plugins are broken).
  7. 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.
  8. Edit MANIFEST.MF and add the new jar (specified in build.properties) to the classpath.

Note that if you want to run the tests locally through the testing framework (a good idea in order to ensure that everything is set up properly), do this:

Adding third party binary plugins for distribution

AJDT does not do this yet, but we may choose to bundle our own version of Equinox Aspects. If we do this, then how to do this for other third party plugins will be described here.