The BCEL-builder module

Java 5 support

The best way to see how it works is look in the testcases. The only feature that is definetly not implemented yet is package level annotations. What is working is:

• You can ask a type: are you an annotation type? are you an enum type?
• You can ask a method: were you defined with varargs? Are you a bridge method?
• All annotation values types are supported (primitive, string, array, enum, annotation, class).
• Runtime visible and invisible annotations are supported.
• Annotations are accessible on types, methods, fields.
• Parameter annotations are accessible on methods.
• You can programmatically construct annotations and attach them to types, methods, fields.
• You can construct parameter annotations and add them to methods.
• The EnclosingMethod attribute is supported (it is used to let you know the containing method for local/anonymous types)
• The LocalVariableTypeTable attribute is supported (used for generics to tell you the original variable signature)

All this is implemented without using any Java 5 APIs.

The contents of this directory are:

• This file
• src -- contains the source for BCEL, a modified variant of BCEL 5.1 that includes bug fixes and Java 5 support
• verifier-src -- contains the source for the bcel verifier package, something used by tests but not packaged and distributed (at the moment).
• testsrc -- JUnit test cases for the Java 5 support
• testdata -- Java5 testcode that can be built using the build.xml script in the testdata directory (see note on this below)
• build.xml -- an ant script for manipulating the src folder, possibly useful if ever merging a base BCEL version

Development Process

We can now follow normal TDD for this. Add a JUnit testcase to the testsrc folder, plus any associated test materials into the testdata directory. Then change BCEL to get your test passing, when you are happy with the result (i.e. all the tests in the bcel-builder module are passing), you should execute the build.xml script whose default target will package up bcel (and bcel src) and deliver it into the lib module, the rest of AspectJ is driven off the version of bcel in the lib/bcel folder - it is *not* driven off the bcel-builder code (we could choose to change that sometime later).

Once you have done this execute all the tests for AspectJ, if they all pass you can check in your mods for bcel-builder and to the lib project.

testdata