2.2.0

Don't configure jacoco to exclude generated files in gradle 5+ (#107)

The logic doesn't work in gradle 5 anymore, so we're turning it off for now.
If there is a need for this in the future, we can look at re-implementing the logic, although gradle 5.2+ now writes generated sources into a separate directory, so from that point on it might be a lot easier to just exclude compileOptions.annotationProcessorGeneratedSourcesDirectory.

2.1.0

[improvement] Configure annotation processor classpath explicitly in IDEA (#97)

gradle-processors v2.0.0

• [break] Stop making compileOnly extend annotationProcessor (#91)

gradle-processors v1.4.0

Stop manipulating .idea/compiler.xml when importing from IDEA (#90)

Motivation

If importing from IntelliJ, the annotation processor needs to be configured differently based on whether you're importing using 'separate source sets' or not. The plugin only worked in the former case.

In order to avoid further complexity to make both cases work, we've decided to remove that logic altogether. The plugin now only supports out-of-the-box configuration when calling ./gradlew idea.

gradle-processors v1.3.0

Rely on gradle 4.6+ annotationProcessor logic if that configuration exists (#83)

gradle-processors v1.2.18

Only modify configuration once java plugin has been applied (#82)

gradle-processors v1.2.17

• [fix] compatibility with Gradle 4.6's annotationProcessor configuration (#81)

gradle-processors v1.2.16

#80 Lazily create processorPath tasks

gradle-processors v1.2.15

This release will now only modify IDEA's .idea/compiler.xml file if Gradle is run from within IDEA itself

gradle-processors v1.2.14

This release fixes a path escaping issue on Windows