-
Gradle 4.7+ has a new feature to let annotation processors run incrementally. In order to make that work, Immutables has to tell Gradle how its annotation processor behave during execution.
For det…
-
Our project (unfortunately) still uses [AutoFactory](https://github.com/google/auto/tree/master/factory), and a couple other legacy in-house APs that require enabling '[non-existent type correction](h…
-
I develop a project which uses annotation processing to instrument all classes, even those without any annotations.
I have noticed this issue that from version 1.16.22 +, with introduction of this co…
-
Hi team 👋,
I was recently aware of this build server and was playing around with it.
I tested it toward this project: https://github.com/mapstruct/mapstruct-examples/tree/main/mapstruct-on-gradl…
jdneo updated
1 month ago
-
By default, the compiler attempts to discover annotation processors from the classpath. This can have side effect on code that is generated ahead of time.
Adding `-proc:none` in the Maven and Grad…
-
When using buck with the error prone java compiler, if a `java_library` has annotation processors (legacy or modern), buck fails with
```
Buck encountered an internal error
java.nio.file.NoSuchFi…
-
For Kotlin projects, Toothpick currently makes use of KAPT. This is generally quite slow since it requires generating Java stubs before the annotation processing step.
[KSP](https://github.com/goog…
-
I encountered an issue while trying to create a fix for our generated enums https://github.com/nelmio/NelmioApiDocBundle/issues/2177
While doing this I noticed that the `AugmentProperties` processo…
-
### Component(s)
receiver/receivercreator
### Is your feature request related to a problem? Please describe.
This issue proposes to add support for a hints/suggestions based autodiscovery mec…
-
Due to the error-tolerant nature of annotation processing, it's unclear when and how to warn about invalid source inputs. A verbose mode to dump all findings by KSP can be useful when debugging proces…