PDE, or the Plugin Development Environment, is the tool set that helps developers build plugins for the Eclipse platform itself. In Eclipse 3.5 and earlier, AJDT shipped with its own version of the PDE tools (AJDT-PDE) that were largely a copy of Eclipse's PDE, but with a few key changes so that a different compiler could be plugged in. It is an understatement to say that this was inefficient. The AJDT-PDE had to be re-created for each point release of Eclipse so that it could be re-based off of the new version of PDE. This process was fallible and inevitably, some features of PDE were missing or broken in AJDT-PDE.
I have been working with the PDE team to create a more sustainable solution to AspectJ-aware PDE builds. From AJDT for Eclipse 3.6 and onwards, the AJDT-PDE will be removed. The AspectJ-aware export wizards will be deprecated and the
org.eclipse.ajdt.pde.buildplugin will be redundant. Instead, users can use the standard PDE build, with the following changes to the
build.propertiesfile of your plugin project:
The first line specifies that the AspectJ compiler should be used instead of the Java compiler. The second line specifies what file types should be considered source files. And optionally, you can specify a number of command line arguments using the
compilerArgproperty. Only AspectJ-specific arguments like
aspectpathneed to be specified here. For all standard Java options, like
targetyou can use the standard PDE-Java options
From here, you can use the standard PDE export wizards or PDE headless build scripts to build your project. That's it. There is now nothing special needed for AspectJ-aware PDE builds.
Furthermore, it is possible to create your own compiler adapter so that you can use your own custom compiler for your own JVM language (and avoid using javac). You need to do the following:
org.apache.tools.ant.taskdefs.compilers.CompilerAdapterand delegate to the compiler of your choice
- Ensure that this new compiler adapter is on the ant classpath. I recommend using a
org.eclipse.ant.core.extraClasspathEntriesextension point so that your plugin automatically contributes the classpath to Eclipse's ant runtime. But, you could also specify it in your global ant classpath properties page.
- In your build.properties file, fill in the proper values for the compilerAdapter, the sourceFileExtensions, and the compilerArg properties.
That's really all there is to it. For all the gory details on how this works see Bug 303960.