Looks like you are using gradle 3.5, rather than the gradle wrapper we have checked in?
For me, the buildSrc targets all report that they are up to date: ./gradlew -DdistributedTest.single=BasicDUnitTest geode-core:distributedTest Picked up JAVA_TOOL_OPTIONS: :buildSrc:compileJava UP-TO-DATE :buildSrc:compileGroovy UP-TO-DATE :buildSrc:processResources UP-TO-DATE :buildSrc:classes UP-TO-DATE :buildSrc:jar UP-TO-DATE :buildSrc:assemble UP-TO-DATE :buildSrc:compileTestJava UP-TO-DATE :buildSrc:compileTestGroovy UP-TO-DATE :buildSrc:processTestResources UP-TO-DATE :buildSrc:testClasses UP-TO-DATE :buildSrc:test UP-TO-DATE :buildSrc:check UP-TO-DATE :buildSrc:build UP-TO-DATE On Mon, Jan 30, 2017 at 5:27 PM, Kirk Lund <kl...@apache.org> wrote: > Right after I do a clean build, if I then execute a single dunit test via > gradle, buildSrc recompiles again. Is this intentional? Is there a way to > configure our build to not recompile it again? > > BUILD SUCCESSFUL > > Total time: 4 mins 34.685 secs > <klund@Kirks-MacBook-Pro>/Users/klund/dev/geode_CLEAN [1424]$ gradle > -DdistributedTest.single=BasicDUnitTest geode-core:distributedTest > Starting a Gradle Daemon (subsequent builds will be faster) > Generating JAR file 'gradle-api-3.5-20170131004703+0000.jar' > Cleaned up directory > '/Users/klund/dev/geode_CLEAN/buildSrc/build/classes/main' > :buildSrc:clean > :buildSrc:compileJava NO-SOURCE > > Loading > buildSrc > :buildSrc:compileGroovy >
