-
Notifications
You must be signed in to change notification settings - Fork 23
Run annotation processors as part of the gradle idea task #76
Comments
Running javac is the responsibility of IntelliJ, not Gradle. You don't want a code typo preventing you generating the IntelliJ project. |
I guess you're talking about the implementation? The way I imagined it,
gradle already runs the annotation processors as part of compileJava, it
would just need to do the exact same thing but using the intellij "out"
directory, instead of its own "build" directory.
…On 14 Aug 2017 3:27 pm, "Alice Purcell" ***@***.***> wrote:
Running javac is the responsibility of IntelliJ, not Gradle. You don't
want a code typo preventing you generating the IntelliJ project.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#76 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABr34p1RL5qTXmJufWJ7fAEu0KVPh_FNks5sYFlqgaJpZM4O2aho>
.
|
No, I mean |
I am seeking help here as i couldn't find any valuable resource else where. I am trying to have my custom plugin create a |
Yep this is possible and here is my task configs
Hope this could be helpful to someone. |
Current behavior: when switching to a new branch that has different dependencies, I need to run
gradle idea
to fetch those, and then I need to run Rebuild Project in IntelliJ to run the annotation processors again.Desired behavior:
gradle idea
also runs the annotation processors such that checking out a commit and runninggradle idea
is sufficient to start coding.The text was updated successfully, but these errors were encountered: