Why does including the ‘org.postgresql:postgresql:9.3-1102-jdbc41’ as a testCompile dependency make my project build time increase by 130 seconds or more?
In answer to the potential question as to why I picked the "testCompile"group, after reading the Gradle API documentation it stated the default behavior of the testCompile group is to include the dependency in the compile, runtime, and testRuntime groups, which is what I think I want. I need the JAR file at runtime for JDBC. Is the testCompile group an appropriate decision?
here is my build.gradle: buildscript {
ext {
springBootVersion = ‘1.1.8.RELEASE’
}
repositories {
mavenCentral()
}
dependencies {
classpath(“org.springframework.boot:spring-boot-gradle-plugin:${springBootVersion}”)
} }
apply plugin: ‘java’ apply plugin: ‘eclipse’ apply plugin: ‘idea’ apply plugin: ‘spring-boot’
jar {
baseName = ‘report.api’
version = ‘0.0.1-SNAPSHOT’ } sourceCompatibility = 1.8 targetCompatibility = 1.8
repositories {
mavenCentral() }
dependencies {
compile(“org.springframework.boot:spring-boot-starter-data-rest”)
compile(“org.springframework.boot:spring-boot-starter-aop”)
compile(“org.springframework.boot:spring-boot-starter-web”)
compile(“org.springframework.boot:spring-boot-starter-data-jpa”)
compile(“org.springframework.boot:spring-boot-starter-jdbc”)
compile(“org.springframework.boot:spring-boot-starter-actuator”)
testRuntime(“org.postgresql:postgresql:9.3-1102-jdbc41”)
testCompile(“org.springframework.boot:spring-boot-starter-test”) }
eclipse {
classpath {
containers.remove(‘org.eclipse.jdt.launching.JRE_CONTAINER’)
containers ‘org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-1.8’
} }
task wrapper(type: Wrapper) {
gradleVersion = ‘1.12’ }