When replacing this deprecated method, which shall we prefer: testClassesDirs = files(sourceSets.integrationTest.output.classesDir) or testClassesDirs = sourceSets.integrationTest.output Strictly speaking, the latter will also bring the resources into the classpath. Is that a good thing?

Would be nice going forward to have the typical replacements mentioned in the deprecated methods javadoc.

I had a similar problem when bumping from an old Gradle 2.10 to current 5.2.1 : task integrationTest(type:Test) { testClassesDir = project.sourceSets.integrationTest.output.classesDir Could not get unknown property ‘classesDir’ for integration test classes of type org.gradle.api.internal.task…

Thank you So Much for this post.

Gradle 4 - replacing deprecated Test::testClassesDir

Help/Discuss

sterling (Sterling Greene) May 31, 2017, 1:55pm 2

Neither

testClassesDirs = sourceSets.integrationTest.output.classesDirs

If you used multiple languages for the same source set, they could use separate output directories.

Topic		Replies	Views
Gradle upgrade to 5.1.1 with classesDir into classesDirs Help/Discuss	2	4526	March 29, 2019
testClassesDirs() is a mystery Help/Discuss	4	7139	July 19, 2017
Gradle 4 SourceSetOutput.setClassesDir deprecated Help/Discuss	1	5974	June 22, 2017
Could not get unknown property 'classesDir' for main classes of type org.gradle.api.internal.tasks.DefaultSourceSetOutput Help/Discuss	7	39329	February 17, 2020
Balancing deprecation of SourceSetOutput#classesDir and other parts of Gradle that only accept a dir (File) Help/Discuss	1	692	January 2, 2018

Gradle 4 - replacing deprecated Test::testClassesDir

Related topics