## org.aspectj.lib library module

This module has source for both `{AspectJ}/lib/aspectjlib.jar` and `{AspectJ}/docs/aspectjlib/*`.

### Building {AspectJ}/lib/aspectjlib.jar

This module is compiled using AspectJ, both in Eclipse and with Ant. The Eclipse support is defined as usual in .classpath and .project. The Ant build support in ../build/build.xml is limited:

- This module is built and published as `{aspectj}/lib/aspectjlib.jar`. This happens automatically, with no explicit Ant script. The Builder.java task uses `moduleAliasFor(String)` to map from the name of the empty file ../build/products/tools/dist/lib/aspectjlib.jar back to the module output ../aj-build/jars/org.aspectj.lib.jar.
- The AspectJ support compiles only source files in src/
- It does not use inpath, aspectpath, or any other aspectj-specific option
- All non-Java (resource) files in the source directory will be included in the library.
- There should be no dependencies. Any libraries or modules on the Java classpath would be included in the shipped library.
- This is built using the release of AspectJ in ../lib/aspectj.

### Building {AspectJ}/examples/aspectjlib/*

The docs build script ../docs/build.xml is responsible for assembling sources from this directory into the docs directory. It relies on the name of the source directory and build script. Also, `Builder.java` is designed to try to use any `build.xml` to build the module, but Ant builds are now disabled. So if you change the build script name or the source directory names, update the docs build script and the builder as needed.

The build-aspectjlib.xml script looks for an AspectJ lib directory from either the distribution (aspectj/docs/aspectjlib) or from the CVS tree (modules/org.aspectj.lib), so the script can be tested in situ.