mirror of
https://github.com/spring-projects/spring-security.git
synced 2026-03-30 14:08:11 +00:00
We should not use subprojects to perform configuration becaause it does not allow for lazy loading and it can cause ordering problems. In this case, the toolchain was not being used but instead it was using the JAVA_HOME. By splitting the configuration into a plugin and applying it to each project it fixes the toolchain configuration
33 lines
1.4 KiB
Groovy
33 lines
1.4 KiB
Groovy
apply plugin: 'io.spring.convention.spring-test'
|
|
apply plugin: 'java-toolchain'
|
|
apply plugin: 'test-compile-target-jdk25'
|
|
|
|
dependencies {
|
|
implementation platform(project(":spring-security-dependencies"))
|
|
implementation project(':spring-security-core')
|
|
implementation project(':spring-security-access')
|
|
implementation 'org.python:jython'
|
|
implementation 'org.springframework:spring-aop'
|
|
implementation 'org.springframework:spring-beans'
|
|
implementation 'org.springframework:spring-context'
|
|
implementation 'org.springframework:spring-tx'
|
|
|
|
testImplementation project(path: ':spring-security-web')
|
|
testImplementation project(path: ':spring-security-web', configuration: 'tests')
|
|
testImplementation 'jakarta.servlet:jakarta.servlet-api'
|
|
testImplementation 'org.springframework:spring-web'
|
|
testImplementation "org.assertj:assertj-core"
|
|
testImplementation "org.junit.jupiter:junit-jupiter-api"
|
|
testImplementation "org.junit.jupiter:junit-jupiter-params"
|
|
testImplementation "org.junit.jupiter:junit-jupiter-engine"
|
|
testImplementation "org.mockito:mockito-core"
|
|
testImplementation "org.mockito:mockito-junit-jupiter"
|
|
testImplementation "org.springframework:spring-test"
|
|
|
|
testRuntimeOnly project(':spring-security-config')
|
|
testRuntimeOnly 'org.aspectj:aspectjweaver'
|
|
testRuntimeOnly 'org.junit.platform:junit-platform-launcher'
|
|
}
|
|
|
|
System.setProperty('python.cachedir.skip', 'true')
|