But even with the problem class removed, it isn't generating the correct sources. And I am having a lot of difficulty figuring out how to debug this when I run it command line, so it's not a very effective debugging process adding in printlns as I go along but without being able to inspect any vars, or even know which implementations are being called for what.
I like your suggesting of trying to jarjar aspectj, but not sure which pkgs need to be modified: aspectjrt, aspectjtools, or aspectjweaver? I actually tried to jarjar all 3, just to be safe, but when I run ajc with lombok, I get the following error:
[WARNING] You aren't using a compiler supported by lombok, so lombok will not work and has been disabled.
Your processor is: org.aspectj.org.eclipse.jdt.internal.compiler.apt.dispatch.BatchProcessingEnvImpl
Lombok supports: sun/apple javac 1.6, ECJ
Which to me looks like I missed something when I jarjar'ed the pkgs.
But my rule was pretty basic:
rule org.aspectj.org.eclipse.jdt.* org.eclipse.jdt.@1
java -jar ~/Documents/Dev/libs/jarjar/jarjar-1.4.jar process lombok.jarjar.txt ../1.8.2/aspectjtools-1.8.2.jar aspectjtools-1.8.2_lombok.jar
And then pointed to the newly created 1.8.2_lombok version in my maven pom.
So I'm a little lost/confused at this point. Not sure what/where to try to tackle next. Was hoping to get some more direction from Reinier Zwitserloot or Roel Spilker (the lead devs) but haven't heard anything back from them yet.
Am open to any suggestions. I was really hoping to use Lombok instead of Roo (had an unpleasant Roo experience) and not using any spring-data stuff, so figured lombok would be easier. But I don't know if I'll ever get there.