Hi Andy,
Just to keep you updated, I managed to get a debug session working with a remote debugger. Indeed, I had incorrectly jarjar'ed the aj lib, and once I re jarjar'ed it, I got lombok to recognize it. Unfortunately though, it still is not lombok'ing.
That being said, I'm having a lot of difficulty in debugging the lombok code. It uses a bunch of jdt libs to compile, but they aren't the actual ones being used during the debug process (I presume it is using different versions), so stepping through code is a nightmare as the source lines don't actually match up with the remote process being debugged. I have to dig around a little more there and see if I can find out why.
In the meantime, I've posted some questions to the lombok list hoping others can point me in a helpful debug process, but so far am awaiting a response.
The only thing I noticed from a quick look is the entry point into the lombok lib from ajc and from javac seem to be from two different places. Is that possible? Lombok process gets bootstrapped via APT (from what I can tell). Is it possible that ajc launches the APT process from a different point than javac?
Thanks,
Eric