AspectJ Development Tools v1.1.4 Release Notes

Changes from 1.1.3 release

Bugs fixed

Of note

Changes from 1.1.2 release

Known limitations in this release:

Changes from 0.6.1 release

Changes from 0.6.0 release

Changes from 0.5.2 release

Changes from 0.5.1 release

Changes from 0.5.0 release

Installation verification instructions

  1. Start Eclipse.

  2. Confirm that both the AspectJ and AJDT plugins have been successfully installed:



Post Installation Customization (important)

Configuring the editor:

You need to configure Eclipse to use the AspectJ/Java editor for .java source files (in place of the Java editor supplied by JDT).










Adding the New Aspect Wizard Shortcut:




Here's how it looks:





Disabling warnings about unused imports in AspectJ files:

By default, the compiler is setup to report any unused imports as warnings. This can cause a problem if you are working in an aspect. Here is an example where the warning is appearing for LogAdapter.java (part of the figures demo):




The compiler can be configured so that it does not report these warnings - select "Preferences" from the "Window" menu and then expand the "Java" node. Click on "Compiler" and then under the first tab "Problems" there is a setting for "Unused imports:" - change it from "Warning" to "Ignore". The next image shows where the option can be found in the preferences page:






When you click Apply or OK to confirm this setting, you will get a message indicating that due to a change in compiler options, a full rebuild is necessary, click OK to perform this rebuild and the warning should disappear.

Disabling early problem indication for AspectJ elements:

The early problem indication feature of the JDT underlines potential errors in the editor as you type (before compilation). This feature is not AspectJ-aware. As a result, AspectJ keywords may be highlighted as errors by underlining with a req “squiggle”(see below):




This feature is perfectly harmless, but can be irritating. You can disable these annotations by selecting "Preferences" from the "Window" menu and then expanding the "Java" node. Click on "Editor" and then select the "Annotations" tab. Finally, deselect the "Analyse annotations while typing" option and press apply. This next image shows where the option can be found in the preferences page:




Things you need to know about the plugin.

Automatic build suppression

By default, AJDT suppresses automatic builds on resource modification (for AspectJ projects only) since AspectJ does not yet support incremental compilation. To build an AspectJ project, either select the project in the packages view and then select “Rebuild” from the project menu, or use the AspectJ build button:




AJDT supports multiple build configurations within a project (created using the New Build Configuration wizard). To select an alternate configuration for building, use the pulldown beside the build button:




No Eager Parsing

Currently there is no eager parsing support for AJDT. A consequence of this is that the outline view does not update as you edit, but instead is updated as a result of performing a build (compilation).

Debugging

Breakpoints can be set in Java classes (but not in aspects). To set a breakpoint, double-click in the editor margin (the context menu option “Add Breakpoint” does not work yet). See the FAQ for more details

Using existing AspectJ .lst files

The AspectJ command line tools support a richer build configuration file format than AJDT. If you experience problems using an existing .lst file with a project inside Eclipse then opening the file in the Build Configuration Editor (double-click in packages view for example) and saving it again should correct most problems.