Cool. Looks like the right approach to me. The problem I have with 'just recompiling javac' is that it's not very friendly in a typical dev environment.
1. I have to tell my boss we are using a 'custom' java compiler. 2. I have to make sure that is 'patched' everywhere. On dev machines and on CI servers etc. 3. When someone downloads the latest JDK, a re-patch is required. It increases the risk of getting 'stuck on a version'. The Lombok approach works because it can be seen as just another dependency to your project. Not hacky shenanigans. If the trickery happens at runtime it makes your build process repeatable and predictable. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
