If you have problems with the browser not solved by the documentation, please try to see if you have the same problems when running ajc directly on the command line.
If the problem occurs on the command line also, then the problem is not in the browser. (It may be in the compiler; please send bug reports.)
If the problem does not occur on the command line, then it may lie in the parameters you are supplying in the build options.
If the build options look correct and the problem only occurs when building from the browser, then please submit a bug report.
For the most up-to-date information on known problems, see the bug database for unresolved compiler bugs or IDE bugs .
Memory and forking: Users email most about the browser task running out of memory. This is not a problem with the browser; some compiles take a lot of memory, often more than similar compiles using javac. The browser does not support forking, so the only solution is to edit the java command line or script that launches the browser to add memory.
Editing build configuration files: this is not currently supported.
The structure model is incomplete after incremental compiles. To get a complete structure model requires a full build.
If you change the output directory, you must do a full build.
You can send email to aspectj-users@dev.eclipse.org. (Do join the list to participate!) We also welcome any bug reports, patches, and feature requests; you can submit them to the bug database at http://bugs.eclipse.org/bugs using the AspectJ product and IDE component.