Stefan Oehme

The problem is that the checker plugin overwrites both the processor path and which processors to use. As a result no other annotation processors (e.g. the one from Glide) will...

I think so. But there is a conceptual problem: The plugin sets the `-processor` option based on the checkers selected in the extension. That will deactivate all other processors. I'm...

Yeah that document assumes no other annotation processors.

I just looked at their code base. They don't have any descriptors for auto discovery (intentionally). So what you can do is write a task that generates a file called...

Also while you're changing it - Passing the -processorpath option as a string is deprecated, because we have a DSL method (options.annotationProcessorPath) for it. That option will work properly with...

Same goes for the requireJs tasks. I'd be willing to correct the usage of extensions for that, so you can fix it accordingly for all others.

I think `@FluentAccessors` is the right term for this. Builders are just one use case for them. I'm open for a contribution, you can take the implementation of `@Accessors` as...

I think this is pretty well covered by Xtend's `FinalFieldsConstructor` (which is equivalent to `RequiredArgsConstructor`). - a `NoArgsConstructor` is so short in Xtend (`new() {}`) that I don't think it...

I'd rather have something like `@FactoryMethod` instead of an argument on the constructor annotation.

Value objects and inheritance do not mix well. Through subclassing, clients can break the contract of immutabililty. So other clients of the class can no longer be sure that all...