Passing classpath in file by default

README.md

@@ -97,7 +97,7 @@ to add integration tests located in a different source set)
 another Java processes for mutation testing execution and usually `jvmArgs` should be used to for example increase maximum memory size
 (see [#7](https://github.com/szpak/gradle-pitest-plugin/issues/7));
  - `additionalMutableCodePaths` - additional classes to mutate (useful for integration tests with production code in a different module - see [#25](https://github.com/szpak/gradle-pitest-plugin/issues/25))
- - `useClasspathFile` - enables passing additional classpath as a file content (useful for Windows users with lots of classpath elements, disabled by default)
+ - `useClasspathFile` - enables passing additional classpath as a file content (useful for Windows users with lots of classpath elements, enabled by default)
  - `fileExtensionsToFilter` - provides ability to filter additional file extensions from PIT classpath (see [#53](https://github.com/szpak/gradle-pitest-plugin/issues/53))
 
 For example:

src/main/groovy/info/solidsoft/gradle/pitest/PitestPlugin.groovy

@@ -111,7 +111,7 @@ class PitestPlugin implements Plugin<Project> {
         extension.testSourceSets.set([javaSourceSets.getByName(SourceSet.TEST_SOURCE_SET_NAME)])
         extension.mainSourceSets.set([javaSourceSets.getByName(SourceSet.MAIN_SOURCE_SET_NAME)])
         extension.fileExtensionsToFilter.set(DEFAULT_FILE_EXTENSIONS_TO_FILTER_FROM_CLASSPATH)
-        extension.useClasspathFile.set(false)
+        extension.useClasspathFile.set(true)
         extension.verbosity.set("NO_SPINNER")
     }
 

src/test/groovy/info/solidsoft/gradle/pitest/BasicProjectBuilderSpec.groovy

@@ -50,6 +50,7 @@ class BasicProjectBuilderSpec extends Specification {
         pitestConfig = project.getExtensions().getByType(PitestPluginExtension)
 
         project.group = 'test.group'
+        project.pitest.useClasspathFile = false
     }
 
     protected PitestTask getJustOnePitestTaskOrFail() {