Grant Henke has posted comments on this change. ( )

Change subject: [java] Use gradle caching now that it is stable in 4.6

Patch Set 1:

Commit Message:
PS1, Line 7: [java] Use gradle caching now that it is stable in 4.6
> What's the motivation? Can you explain in the commit message?
PS1, Line 9: protobug
> protobuf?
File build-support/jenkins/
PS1, Line 390:      GRADLE_FLAGS="$GRADLE_FLAGS --console=plain --no-daemon 
> Why disable the daemon and caching here? Can you add a comment?
I don't have too but I used it for build isolation. I will add a comment.
File java/gradle/compile.gradle:
PS1, Line 26:   options.compilerArgs << '-proc:none' // Ignore leaked 
annotation processors on the compile classpath.
> What does that error actually mean? What does "leaking" mean in this contex
To see the warning output from gradle run a build on the kudu-hive project 
without this line. Essentially a transitive dependency somewhere in the stack 
added an annotation processor that should not be there. Since we don't sue them 
we are ignoring them.

Here is the gradle documentation on the issue:

To view, visit
To unsubscribe, visit

Gerrit-Project: kudu
Gerrit-Branch: master
Gerrit-MessageType: comment
Gerrit-Change-Id: Ibf5cc3c7a1263b085511c825118fb814e1b65008
Gerrit-Change-Number: 10074
Gerrit-PatchSet: 1
Gerrit-Owner: Grant Henke <>
Gerrit-Reviewer: Adar Dembo <>
Gerrit-Reviewer: Dan Burkert <>
Gerrit-Reviewer: Grant Henke <>
Gerrit-Reviewer: Kudu Jenkins
Gerrit-Comment-Date: Mon, 16 Apr 2018 18:28:24 +0000
Gerrit-HasComments: Yes

Reply via email to