root
/
spring-framework
mirror of https://github.com/spring-projects/spring-framework.git
1
0
Fork 0
Code Issues Actions 6 Packages Projects Releases Wiki Activity
spring-framework/build.gradle

403 lines
15 KiB
Groovy
Raw Normal View History

Use the official SonarQube Gradle plugin Since the build has been upgraded to Gradle 2.10, it's showing the following message: "The 'sonar-runner' plugin has been deprecated and is scheduled to be removed in Gradle 3.0. please use the official plugin from SonarQube" This commit makes use of the "org.sonarqube" Gradle plugin and uprgrades the Jacoco agent version to 0.7.5. See: https://sonar.spring.io/updatecenter/updates See: https://jira.sonarsource.com/browse/SONARJAVA-1091 Closes gh-949
2016-01-06 00:16:39 +08:00
plugins {
Upgrade Gradle plugins
2022-08-04 17:29:34 +08:00
id 'io.spring.dependency-management' version '1.0.12.RELEASE' apply false
Upgrade to nohttp 0.0.10 This upgrade avoids warnings about the following on Gradle 7.1+. - The Report.destination property has been deprecated. - The JavaExec.main property has been deprecated. See gh-26870
2021-09-14 17:24:28 +08:00
id 'io.spring.nohttp' version '0.0.10'
Upgrade Gradle plugins
2022-08-04 17:29:34 +08:00
id 'io.freefair.aspectj' version '6.5.0.3' apply false
Upgrade to Dokka Gradle plugin 1.7.10 Closes gh-28912
2022-08-02 20:24:35 +08:00
id 'org.jetbrains.dokka' version '1.7.10' apply false
Upgrade to Kotlin 1.7.10 Closes gh-28784
2022-07-11 16:12:49 +08:00
id 'org.jetbrains.kotlin.jvm' version '1.7.10' apply false
Upgrade Gradle plugins
2022-08-04 17:29:34 +08:00
id 'org.jetbrains.kotlin.plugin.serialization' version '1.7.10' apply false
Polish Gradle upgrade Closes gh-26870
2021-09-13 15:36:07 +08:00
id 'org.asciidoctor.jvm.convert' version '3.3.2'
id 'org.asciidoctor.jvm.pdf' version '3.3.2'
Upgrade Gradle plugins
2022-08-04 17:29:34 +08:00
id 'org.unbroken-dome.xjc' version '2.0.0' apply false
id 'com.github.ben-manes.versions' version '0.42.0'
id 'com.github.johnrengelman.shadow' version '7.1.2' apply false
id 'de.undercouch.download' version '5.1.0'
id 'me.champeau.jmh' version '0.6.6' apply false
Use Gradle build scans This commit configures Gradle build scans for the Spring Framework build. Scans aren't performed for every build but can be enabled with the following: ``` ./gradlew build --scan ``` Issue: SPR-15885
2017-08-21 20:29:49 +08:00
}
Add sonar integration. This commit configures the SonarRunner plugin so that SonarQube can be used against the project. A few customizations were applied to namely exclude the asm and cglib repackaged classes. Issue: SPR-10766
2014-04-10 17:22:14 +08:00
ext {
Rename non-Framework project modules Prior to this commit, the Spring Framework build would mix proper framework modules (spring-* modules published to maven central) and internal modules such as: * "spring-framework-bom" (which publishes the Framework BOM with all modules) * "spring-core-coroutines" which is an internal modules for Kotlin compilation only This commit renames these modules so that they don't start with "spring-*"; we're also moving the "kotlin-coroutines" module under "spring-core", since it's merged in the resulting JAR. See gh-23282
2019-08-21 20:28:42 +08:00
moduleProjects = subprojects.findAll { it.name.startsWith("spring-") }
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
javaProjects = subprojects - project(":framework-bom")
Upgrade to AspectJ 1.9.4, RxJava 2.2.10, Jetty 9.4.19, Undertow 2.0.22 Includes Hibernate Validator 6.0.17 and renames "withoutJclOverSlf4j".
2019-06-22 22:49:40 +08:00
withoutJclOverSlf4j = {
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
exclude group: "org.slf4j", name: "jcl-over-slf4j"
Remove dependency management noise from POMs Prior to this commit, the generated POMs for Spring Framework modules would contain unneeded/harmful information from the Spring Framework build: 1. The BOM imports applied to each module by the dependency management plugin, for example for Netty or Reactor Netty. Spring should not export that opinion to its POMs. 2. The exclusion of "org.slf4:jcl-over-slf4j" from *all* dependencies, which made the POMs much larger than necessary and suggested to developers that they should exclude it as well when using all those listed dependencies. In fact, only Apache Tiles currently brings that transitively. This commit removes that information from the POMs. The dependencyManagement Gradle plugin is disabled for POM generation and we manually resolve the dependency versions during the generation phase. The Gradle build is streamlined to exclude "org.slf4:jcl-over-slf4j" only when necessary. Issue: SPR-16893
2018-06-11 21:33:05 +08:00
}
Add sonar integration. This commit configures the SonarRunner plugin so that SonarQube can be used against the project. A few customizations were applied to namely exclude the asm and cglib repackaged classes. Issue: SPR-10766
2014-04-10 17:22:14 +08:00
}
Fix missing findbugs dependency for Dokka task
2019-09-03 02:08:34 +08:00
configure(allprojects) { project ->
Consistently use double quotes (even if no interpolation needed) Includes upgrade to Hibernate ORM 5.3.5, EclipseLink 2.7.3, Selenium HtmlUnit Driver 2.32.1, Jetty 9.4.12 RC2.
2018-08-16 21:32:44 +08:00
apply plugin: "io.spring.dependency-management"
Introduce Gradle-based build - Use recent Gradle 1.0-milestone-8 snapshot - Add initial cut of build.gradle able to compile/test all modules - Update .gitignore - Generate Gradle wrapper scripts - Remove all Eclipse metadata files - Temporarily @Ignore tests that do not pass under Gradle
2011-12-15 08:56:31 +08:00
Remove dependency management noise from POMs Prior to this commit, the generated POMs for Spring Framework modules would contain unneeded/harmful information from the Spring Framework build: 1. The BOM imports applied to each module by the dependency management plugin, for example for Netty or Reactor Netty. Spring should not export that opinion to its POMs. 2. The exclusion of "org.slf4:jcl-over-slf4j" from *all* dependencies, which made the POMs much larger than necessary and suggested to developers that they should exclude it as well when using all those listed dependencies. In fact, only Apache Tiles currently brings that transitively. This commit removes that information from the POMs. The dependencyManagement Gradle plugin is disabled for POM generation and we manually resolve the dependency versions during the generation phase. The Gradle build is streamlined to exclude "org.slf4:jcl-over-slf4j" only when necessary. Issue: SPR-16893
2018-06-11 21:33:05 +08:00
dependencyManagement {
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
imports {
Merge branch '5.3.x' # Conflicts: # build.gradle # spring-jms/src/main/java/org/springframework/jms/connection/CachingConnectionFactory.java
2022-06-14 21:14:10 +08:00
mavenBom "com.fasterxml.jackson:jackson-bom:2.13.3"
Upgrade to R2DBC 1.0 Includes Reactor 2022.0.0-M4, Netty 4.1.79, Jetty 11.0.11, Undertow 2.2.18, Hibernate ORM 5.6.10, Checkstyle 10.3.1 Closes gh-28787
2022-07-13 16:23:51 +08:00
mavenBom "io.netty:netty-bom:4.1.79.Final"
mavenBom "io.projectreactor:reactor-bom:2022.0.0-M4"
Upgrade to Tomcat 9.0.62, Jetty 9.4.46, Jetty Reactive HttpClient 1.1.11, Undertow 2.2.17, R2DBC Arabba-SR13, RSocket 1.1.2, OpenPDF 1.3.27, HtmlUnit 2.60, Checkstyle 10.1
2022-04-08 19:00:20 +08:00
mavenBom "io.rsocket:rsocket-bom:1.1.2"
Upgrade to R2DBC 1.0 Includes Reactor 2022.0.0-M4, Netty 4.1.79, Jetty 11.0.11, Undertow 2.2.18, Hibernate ORM 5.6.10, Checkstyle 10.3.1 Closes gh-28787
2022-07-13 16:23:51 +08:00
mavenBom "org.eclipse.jetty:jetty-bom:11.0.11"
Upgrade to Kotlin 1.7.10 Closes gh-28784
2022-07-11 16:12:49 +08:00
mavenBom "org.jetbrains.kotlin:kotlin-bom:1.7.10"
Upgrade to Kotlin 1.7.0 Closes gh-28619
2022-06-14 18:58:20 +08:00
mavenBom "org.jetbrains.kotlinx:kotlinx-coroutines-bom:1.6.2"
mavenBom "org.jetbrains.kotlinx:kotlinx-serialization-bom:1.3.3"
Upgrade to JUnit 5.9 Closes gh-28752
2022-07-27 16:02:34 +08:00
mavenBom "org.junit:junit-bom:5.9.0"
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
}
dependencies {
Upgrade to Log4J 2.18, H2 2.1.214, OpenPDF 1.3.29, XStream 1.4.19, HtmlUnit 2.63, Jetty Reactive HttpClient 1.1.12
2022-07-13 22:48:02 +08:00
dependencySet(group: 'org.apache.logging.log4j', version: '2.18.0') {
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
entry 'log4j-api'
entry 'log4j-core'
entry 'log4j-jul'
Upgrade to Netty 4.1.53 and Tomcat 9.0.39 Correct version declaration for Apache HttpClient 5 and its reactive module.
2020-10-16 18:20:15 +08:00
entry 'log4j-slf4j-impl'
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
}
Upgrade to Groovy 4.0.1, Log4J 2.17.2, SLF4J 1.7.36, Netty 4.1.75, SmallRye Mutiny 1.4, Jetty Reactive HttpClient 3.0.5, Hibernate ORM 5.6.6, Hibernate Validator 7.0.4, Mockito 4.4, HtmlUnit 2.59
2022-03-16 17:32:51 +08:00
dependency "org.slf4j:slf4j-api:1.7.36"
Polish contribution See gh-25078
2020-06-11 00:25:31 +08:00
dependency("com.google.code.findbugs:findbugs:3.0.1") {
exclude group: "dom4j", name: "dom4j"
}
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
dependency "com.google.code.findbugs:jsr305:3.0.2"
Upgrade to AspectJ 1.9.9.1 and JRuby 9.3.4
2022-04-08 19:26:22 +08:00
dependencySet(group: 'org.aspectj', version: '1.9.9.1') {
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
entry 'aspectjrt'
entry 'aspectjtools'
entry 'aspectjweaver'
}
Upgrade to Groovy 4.0.2
2022-05-10 19:40:12 +08:00
dependencySet(group: 'org.apache.groovy', version: '4.0.2') {
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
entry 'groovy'
entry 'groovy-jsr223'
Upgrade to Groovy 3.0.3 (with FindBugs workaround for groovy-templates) Closes gh-24215
2020-04-28 20:00:24 +08:00
entry 'groovy-templates' // requires findbugs for warning-free compilation
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
entry 'groovy-xml'
}
Upgrade to Reactor 2020.0.19 Includes Netty 4.1.77 and RxJava 3.1.4. Closes gh-28437
2022-05-10 19:05:56 +08:00
dependency "io.reactivex.rxjava3:rxjava:3.1.4"
Upgrade to Groovy 4.0.1, Log4J 2.17.2, SLF4J 1.7.36, Netty 4.1.75, SmallRye Mutiny 1.4, Jetty Reactive HttpClient 3.0.5, Hibernate ORM 5.6.6, Hibernate Validator 7.0.4, Mockito 4.4, HtmlUnit 2.59
2022-03-16 17:32:51 +08:00
dependency "io.smallrye.reactive:mutiny:1.4.0"
Upgrade to Protobuf 3.18, Rome 1.16, BlockHound 1.0.6, Caffeine 2.9.2, Groovy 3.0.9, Tomcat 9.0.53
2021-09-27 23:01:18 +08:00
dependency "io.projectreactor.tools:blockhound:1.0.6.RELEASE"
Upgrade to R2DBC 1.0 Includes Reactor 2022.0.0-M4, Netty 4.1.79, Jetty 11.0.11, Undertow 2.2.18, Hibernate ORM 5.6.10, Checkstyle 10.3.1 Closes gh-28787
2022-07-13 16:23:51 +08:00
dependency "io.r2dbc:r2dbc-spi:1.0.0.RELEASE"
dependency "io.r2dbc:r2dbc-spi-test:1.0.0.RELEASE"
dependency "io.r2dbc:r2dbc-h2:1.0.0.RC1"
BlockHoundIntegration for spring-core
2020-02-25 01:00:06 +08:00
Upgrade to SmallRye Mutiny 1.3.1, Aalto 1.3.1, Woodstox 6.2.8
2022-01-26 07:02:12 +08:00
dependency "com.fasterxml:aalto-xml:1.3.1"
Upgrade to Woodstox 6.3, Gson 2.9, Protobuf 3.21.2
2022-07-13 23:10:09 +08:00
dependency("com.fasterxml.woodstox:woodstox-core:6.3.0") {
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
exclude group: "stax", name: "stax-api"
}
Upgrade to Woodstox 6.3, Gson 2.9, Protobuf 3.21.2
2022-07-13 23:10:09 +08:00
dependency "com.google.code.gson:gson:2.9.0"
dependency "com.google.protobuf:protobuf-java-util:3.21.2"
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
dependency "com.googlecode.protobuf-java-format:protobuf-java-format:1.4"
Add module to support testing of generated code Add a new unpublished `spring-core-test` module to support testing of generated code. The module include a `TestCompiler` class which can be used to dynamically compile generated Java code. It also include an AssertJ friendly `SourceFile` class which uses qdox to provide targeted assertions on specific parts of a generated source file. See gh-28120
2022-02-25 13:57:11 +08:00
dependency "com.thoughtworks.qdox:qdox:2.0.1"
Upgrade to Log4J 2.18, H2 2.1.214, OpenPDF 1.3.29, XStream 1.4.19, HtmlUnit 2.63, Jetty Reactive HttpClient 1.1.12
2022-07-13 22:48:02 +08:00
dependency("com.thoughtworks.xstream:xstream:1.4.19") {
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
exclude group: "xpp3", name: "xpp3_min"
exclude group: "xmlpull", name: "xmlpull"
}
Upgrade to Hibernate ORM 5.6.5, Eclipse Yasson 2.0.4, JRuby 9.3.3
2022-01-26 07:24:01 +08:00
dependency "org.eclipse:yasson:2.0.4"
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
dependency("org.codehaus.jettison:jettison:1.3.8") {
exclude group: "stax", name: "stax-api"
}
dependency "org.ogce:xpp3:1.1.6"
Upgrade to SnakeYAML 1.30, MockK 1.12.1, Jetty Reactive HttpClient 1.1.10
2021-12-16 04:51:05 +08:00
dependency "org.yaml:snakeyaml:1.30"
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
Upgrade to Log4J 2.18, H2 2.1.214, OpenPDF 1.3.29, XStream 1.4.19, HtmlUnit 2.63, Jetty Reactive HttpClient 1.1.12
2022-07-13 22:48:02 +08:00
dependency "com.h2database:h2:2.1.214"
Merge branch '5.3.x' # Conflicts: # build.gradle # spring-jms/src/main/java/org/springframework/jms/connection/CachingConnectionFactory.java
2022-06-14 21:14:10 +08:00
dependency "com.github.ben-manes.caffeine:caffeine:3.1.1"
Upgrade to Log4J 2.18, H2 2.1.214, OpenPDF 1.3.29, XStream 1.4.19, HtmlUnit 2.63, Jetty Reactive HttpClient 1.1.12
2022-07-13 22:48:02 +08:00
dependency "com.github.librepdf:openpdf:1.3.29"
Upgrade to Tomcat 9.0.58, Protobuf 3.19.3, Rome 1.18, H2 2.1.210, SLF4J 1.7.35, Mockito 4.3.1, HtmlUnit 2.57, XMLUnit 2.9, Checkstyle 9.2.1
2022-01-26 06:51:22 +08:00
dependency "com.rometools:rome:1.18.0"
Upgrade to POI 5.1
2021-12-16 01:15:39 +08:00
dependency "commons-io:commons-io:2.11.0"
Introduce CLI for triggering AOT test context processing This commit introduces ProcessTestsAheadOfTimeCommand, a command-line application (CLI) that scans the provided classpath roots for Spring integration test classes and then generates AOT artifacts for those test classes in the provided output directories. This CLI is only intended to be used by build tools. Closes gh-28825
2022-08-23 22:05:44 +08:00
dependency "info.picocli:picocli:4.6.3"
Upgrade to Caffeine 3.0.4 and Vavr 0.10.4 Includes removal of unused Hessian dependency.
2021-09-28 00:30:09 +08:00
dependency "io.vavr:vavr:0.10.4"
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
dependency "net.sf.jopt-simple:jopt-simple:5.0.4"
Upgrade to Hibernate ORM 5.4.32, RxJava 3.0.13, Aalto 1.3, Gson 2.8.7, Protobuf 3.17.2, XStream 1.4.17, ActiveMQ 5.16.2, HSQLDB 2.5.2, JRuby 9.2.17, Mockito 3.11, HtmlUnit 2.50, Checkstyle 8.43
2021-06-07 18:28:38 +08:00
dependencySet(group: 'org.apache.activemq', version: '5.16.2') {
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
entry 'activemq-broker'
entry('activemq-kahadb-store') {
exclude group: "org.springframework", name: "spring-context"
}
entry 'activemq-stomp'
}
Upgrade to Commons Pool 2.9
2020-10-13 00:37:36 +08:00
dependency "org.apache.commons:commons-pool2:2.9.0"
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
dependencySet(group: 'org.apache.derby', version: '10.14.2.0') {
entry 'derby'
entry 'derbyclient'
}
Upgrade to Hibernate ORM 5.6.8, POI 5.2.2, Caffeine 3.1
2022-05-06 00:15:32 +08:00
dependency "org.apache.poi:poi-ooxml:5.2.2"
Upgrade to BeanShell 2.0b6
2020-04-08 00:06:43 +08:00
dependency "org.apache-extras.beanshell:bsh:2.0b6"
Upgrade to Hibernate ORM 5.4.30, Tomcat 9.0.44, FreeMarker 2.3.31, Log4J 2.14.1, TestNG 7.4, HtmlUnit 2.48
2021-03-23 06:34:13 +08:00
dependency "org.freemarker:freemarker:2.3.31"
Upgrade to Hibernate ORM 5.4.32, RxJava 3.0.13, Aalto 1.3, Gson 2.8.7, Protobuf 3.17.2, XStream 1.4.17, ActiveMQ 5.16.2, HSQLDB 2.5.2, JRuby 9.2.17, Mockito 3.11, HtmlUnit 2.50, Checkstyle 8.43
2021-06-07 18:28:38 +08:00
dependency "org.hsqldb:hsqldb:2.5.2"
Latest dependency updates (Tomcat 9.0.27, Undertow 2.0.27, RxJava 2.2.13, Gson 2.8.6, Apache Johnzon 1.2.1, Hibernate ORM 5.4.8, EclipseLink 2.7.5, H2 1.4.200, POI 4.1.1, Quartz 2.3.2, WebJars Locator 0.42, HtmlUnit 2.36, Checkstyle 8.26, Mockito 3.1, Objenesis 3.1)
2019-10-30 07:26:45 +08:00
dependency "org.quartz-scheduler:quartz:2.3.2"
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
dependency "org.ehcache:jcache:1.0.1"
dependency "org.ehcache:ehcache:3.4.0"
Upgrade to R2DBC 1.0 Includes Reactor 2022.0.0-M4, Netty 4.1.79, Jetty 11.0.11, Undertow 2.2.18, Hibernate ORM 5.6.10, Checkstyle 10.3.1 Closes gh-28787
2022-07-13 16:23:51 +08:00
dependency "org.hibernate:hibernate-core-jakarta:5.6.10.Final"
Upgrade to Groovy 4.0.1, Log4J 2.17.2, SLF4J 1.7.36, Netty 4.1.75, SmallRye Mutiny 1.4, Jetty Reactive HttpClient 3.0.5, Hibernate ORM 5.6.6, Hibernate Validator 7.0.4, Mockito 4.4, HtmlUnit 2.59
2022-03-16 17:32:51 +08:00
dependency "org.hibernate:hibernate-validator:7.0.4.Final"
Upgrade to Hibernate ORM 5.6 CR1, JRuby 9.3, WebJars Locator 0.48, HtmlUnit 2.53
2021-10-01 20:52:27 +08:00
dependency "org.webjars:webjars-locator-core:0.48"
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
dependency "org.webjars:underscorejs:1.8.3"
Merge branch '5.3.x' # Conflicts: # build.gradle # spring-jms/src/main/java/org/springframework/jms/connection/CachingConnectionFactory.java
2022-06-14 21:14:10 +08:00
dependencySet(group: 'org.apache.tomcat', version: '10.0.22') {
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
entry 'tomcat-util'
entry('tomcat-websocket') {
exclude group: "org.apache.tomcat", name: "tomcat-servlet-api"
Update API version and package references for Jakarta EE 9 Closes gh-27689 See gh-25354
2021-11-17 19:39:23 +08:00
exclude group: "org.apache.tomcat", name: "tomcat-websocket-api"
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
}
}
Merge branch '5.3.x' # Conflicts: # build.gradle # spring-jms/src/main/java/org/springframework/jms/connection/CachingConnectionFactory.java
2022-06-14 21:14:10 +08:00
dependencySet(group: 'org.apache.tomcat.embed', version: '10.0.22') {
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
entry 'tomcat-embed-core'
entry 'tomcat-embed-websocket'
}
Upgrade to R2DBC 1.0 Includes Reactor 2022.0.0-M4, Netty 4.1.79, Jetty 11.0.11, Undertow 2.2.18, Hibernate ORM 5.6.10, Checkstyle 10.3.1 Closes gh-28787
2022-07-13 16:23:51 +08:00
dependencySet(group: 'io.undertow', version: '2.2.18.Final') {
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
entry 'undertow-core'
Remove JamonPerformanceMonitorInterceptor support Includes upgrade to Tomcat 10.0.14, Undertow 2.2.14, Apache HttpClient 5.1.2, Hibernate ORM 5.6.2, Mockito 4.1. Closes gh-27786
2021-12-14 16:46:08 +08:00
entry 'undertow-servlet-jakarta'
entry 'undertow-websockets-jsr-jakarta'
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
}
Merge branch '5.3.x' # Conflicts: # build.gradle # spring-aop/src/main/java/org/springframework/aop/aspectj/AbstractAspectJAdvice.java
2022-07-13 23:08:21 +08:00
dependency "org.eclipse.jetty:jetty-reactive-httpclient:3.0.6"
Upgrade to Checkstyle 9.3, HtmlUnit 2.58, Apache HttpClient 5.1.3
2022-02-05 06:51:23 +08:00
dependency 'org.apache.httpcomponents.client5:httpclient5:5.1.3'
dependency 'org.apache.httpcomponents.core5:httpcore5-reactive:5.1.3'
Upgrade to Tomcat 9.0.40 and Apache HttpClient 4.5.13
2020-11-19 22:09:30 +08:00
dependency("org.apache.httpcomponents:httpclient:4.5.13") {
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
exclude group: "commons-logging", name: "commons-logging"
}
Remove JamonPerformanceMonitorInterceptor support Includes upgrade to Tomcat 10.0.14, Undertow 2.2.14, Apache HttpClient 5.1.2, Hibernate ORM 5.6.2, Mockito 4.1. Closes gh-27786
2021-12-14 16:46:08 +08:00
dependencySet(group: 'com.squareup.okhttp3', version: '3.14.9') {
entry 'okhttp'
entry 'mockwebserver'
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
}
Upgrade to AspectJ 1.9.9.1 and JRuby 9.3.4
2022-04-08 19:26:22 +08:00
dependency "org.jruby:jruby:9.3.4.0"
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
dependency "org.python:jython-standalone:2.7.1"
Upgrade to RxJava 2.2.14, OkHttp 3.14.4, JRuby 9.2.9, Rhino 1.7.11, Awaitility 3.1.6
2019-11-08 05:08:52 +08:00
dependency "org.mozilla:rhino:1.7.11"
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
Upgrade to Dom4j 2.1.3 and Jaxen 1.2.0 Closes gh-25078
2020-05-14 18:57:26 +08:00
dependency("org.dom4j:dom4j:2.1.3") {
Polish Closes gh-27754
2021-12-02 21:23:16 +08:00
exclude group: 'javax.xml.bind', name: "jaxb-api"
Upgrade to Dom4j 2.1.3 and Jaxen 1.2.0 Closes gh-25078
2020-05-14 18:57:26 +08:00
exclude group: "jaxen", name: "jaxen"
exclude group: "net.java.dev.msv", name: "xsdlib"
exclude group: "pull-parser", name: "pull-parser"
exclude group: "xpp3", name: "xpp3"
}
dependency("jaxen:jaxen:1.2.0") {
exclude group: "dom4j", name: "dom4j"
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
}
Upgrade to JUnit 4.13.2 Closes gh-26543
2021-02-14 02:22:16 +08:00
dependency("junit:junit:4.13.2") {
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
exclude group: "org.hamcrest", name: "hamcrest-core"
}
dependency("de.bechte.junit:junit-hierarchicalcontextrunner:4.12.1") {
exclude group: "junit", name: "junit"
}
Upgrade to TestNG 7.6.1
2022-07-05 18:45:39 +08:00
dependency "org.testng:testng:7.6.1"
Upgrade to TestNG Engine 1.0.4
2022-07-05 18:43:05 +08:00
dependency "org.junit.support:testng-engine:1.0.4"
Upgrade to Hamcrest 2.2
2022-06-21 19:48:02 +08:00
dependency "org.hamcrest:hamcrest:2.2"
Upgrade to RxJava 2.2.14, OkHttp 3.14.4, JRuby 9.2.9, Rhino 1.7.11, Awaitility 3.1.6
2019-11-08 05:08:52 +08:00
dependency "org.awaitility:awaitility:3.1.6"
Upgrade to AssertJ 3.23.1
2022-06-04 01:44:34 +08:00
dependency "org.assertj:assertj-core:3.23.1"
Upgrade to Tomcat 9.0.58, Protobuf 3.19.3, Rome 1.18, H2 2.1.210, SLF4J 1.7.35, Mockito 4.3.1, HtmlUnit 2.57, XMLUnit 2.9, Checkstyle 9.2.1
2022-01-26 06:51:22 +08:00
dependencySet(group: 'org.xmlunit', version: '2.9.0') {
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
entry 'xmlunit-assertj'
entry('xmlunit-matchers') {
exclude group: "org.hamcrest", name: "hamcrest-core"
}
}
Upgrade to Tomcat 9.0.64, Jackson 2.12.7, Apache Johnzon 1.2.18, OpenPDF 1.3.28, H2 2.1.212, Mockito 4.6.1, HtmlUnit 2.62, Checkstyle 10.3
2022-06-14 21:10:17 +08:00
dependencySet(group: 'org.mockito', version: '4.6.1') {
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
entry('mockito-core') {
exclude group: "org.hamcrest", name: "hamcrest-core"
}
entry 'mockito-junit-jupiter'
}
Upgrade to SnakeYAML 1.30, MockK 1.12.1, Jetty Reactive HttpClient 1.1.10
2021-12-16 04:51:05 +08:00
dependency "io.mockk:mockk:1.12.1"
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
Upgrade to Log4J 2.18, H2 2.1.214, OpenPDF 1.3.29, XStream 1.4.19, HtmlUnit 2.63, Jetty Reactive HttpClient 1.1.12
2022-07-13 22:48:02 +08:00
dependency("net.sourceforge.htmlunit:htmlunit:2.63.0") {
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
exclude group: "commons-logging", name: "commons-logging"
}
Upgrade to Log4J 2.18, H2 2.1.214, OpenPDF 1.3.29, XStream 1.4.19, HtmlUnit 2.63, Jetty Reactive HttpClient 1.1.12
2022-07-13 22:48:02 +08:00
dependency("org.seleniumhq.selenium:htmlunit-driver:2.63.0") {
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
exclude group: "commons-logging", name: "commons-logging"
}
dependency("org.seleniumhq.selenium:selenium-java:3.141.59") {
exclude group: "commons-logging", name: "commons-logging"
exclude group: "io.netty", name: "netty"
}
dependency "org.skyscreamer:jsonassert:1.5.0"
Upgrade to Netty 4.1.68, Jackson 2.12.5, Mockito 3.12.4, MockK 1.12, JsonPath 2.6
2021-09-14 00:14:05 +08:00
dependency "com.jayway.jsonpath:json-path:2.6.0"
Update to Bouncycastle 1.71
2022-06-16 09:21:41 +08:00
dependency "org.bouncycastle:bcpkix-jdk18on:1.71"
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
Jakarta EE 9 migration Upgrades many dependency declarations; removes old EJB 2.x support and outdated Servlet-based integrations (Commons FileUpload, FreeMarker JSP support, Tiles). Closes gh-22093 Closes gh-25354 Closes gh-26185 Closes gh-27423 See gh-27424
2021-09-17 15:14:07 +08:00
dependency "javax.cache:cache-api:1.1.1"
dependency "javax.money:money-api:1.1"
dependency "org.javamoney:moneta:1.4.2"
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
Jakarta EE 9 migration Upgrades many dependency declarations; removes old EJB 2.x support and outdated Servlet-based integrations (Commons FileUpload, FreeMarker JSP support, Tiles). Closes gh-22093 Closes gh-25354 Closes gh-26185 Closes gh-27423 See gh-27424
2021-09-17 15:14:07 +08:00
dependency "jakarta.activation:jakarta.activation-api:2.0.1"
dependency "jakarta.annotation:jakarta.annotation-api:2.0.0"
dependency "jakarta.ejb:jakarta.ejb-api:4.0.0"
dependency "jakarta.el:jakarta.el-api:4.0.0"
dependency "jakarta.enterprise.concurrent:jakarta.enterprise.concurrent-api:2.0.0"
dependency "jakarta.faces:jakarta.faces-api:3.0.0"
dependency "jakarta.inject:jakarta.inject-api:2.0.0"
dependency "jakarta.inject:jakarta.inject-tck:2.0.1"
dependency "jakarta.interceptor:jakarta.interceptor-api:2.0.0"
dependency "jakarta.jms:jakarta.jms-api:3.0.0"
dependency "jakarta.json:jakarta.json-api:2.0.1"
dependency "jakarta.json.bind:jakarta.json.bind-api:2.0.0"
dependency "jakarta.mail:jakarta.mail-api:2.0.1"
dependency "jakarta.persistence:jakarta.persistence-api:3.0.0"
dependency "jakarta.resource:jakarta.resource-api:2.0.0"
dependency "jakarta.servlet:jakarta.servlet-api:5.0.0"
dependency "jakarta.servlet.jsp:jakarta.servlet.jsp-api:3.0.0"
dependency "jakarta.servlet.jsp.jstl:jakarta.servlet.jsp.jstl-api:2.0.0"
dependency "jakarta.transaction:jakarta.transaction-api:2.0.0"
dependency "jakarta.validation:jakarta.validation-api:3.0.0"
dependency "jakarta.websocket:jakarta.websocket-api:2.0.0"
dependency "jakarta.xml.bind:jakarta.xml.bind-api:3.0.1"
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
Jakarta EE 9 migration Upgrades many dependency declarations; removes old EJB 2.x support and outdated Servlet-based integrations (Commons FileUpload, FreeMarker JSP support, Tiles). Closes gh-22093 Closes gh-25354 Closes gh-26185 Closes gh-27423 See gh-27424
2021-09-17 15:14:07 +08:00
dependency "com.sun.activation:jakarta.activation:2.0.1"
dependency "com.sun.mail:jakarta.mail:2.0.1"
dependencySet(group: 'com.sun.xml.bind', version: '3.0.2') {
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
entry 'jaxb-core'
entry 'jaxb-impl'
entry 'jaxb-xjc'
}
// Substitute for "javax.management:jmxremote_optional:1.0.1_04" which
// is not available on Maven Central
dependency "org.glassfish.external:opendmk_jmxremote_optional_jar:1.0-b01-ea"
Jakarta EE 9 migration Upgrades many dependency declarations; removes old EJB 2.x support and outdated Servlet-based integrations (Commons FileUpload, FreeMarker JSP support, Tiles). Closes gh-22093 Closes gh-25354 Closes gh-26185 Closes gh-27423 See gh-27424
2021-09-17 15:14:07 +08:00
dependency "org.glassfish:jakarta.el:4.0.2"
dependency "org.glassfish.tyrus:tyrus-container-servlet:2.0.1"
dependency "org.eclipse.persistence:org.eclipse.persistence.jpa:3.0.2"
Replace build-time initialization by constant fields This commit leverages a subset of @philwebb initial experimentation to compute at build time the value of specific boolean static fields in native images. This enhancement is implemented for now as a GraalVM feature. The goal here is to keep an optimized footprint via build time code removal without leveraging build-time class initialization which is known for the blocking compatibility issues it introduces due to its viral nature. For now, the static fields initialized at build time with native are: - NativeDetector#imageCode - Fields with a name ending by "Present" in "org.springframework" package typically used for classpath check with ClassUtils#isPresent Closes gh-28624
2022-06-22 18:17:40 +08:00
dependency "org.graalvm.nativeimage:svm:22.1.0.1"
Remove dependency management noise from POMs Prior to this commit, the generated POMs for Spring Framework modules would contain unneeded/harmful information from the Spring Framework build: 1. The BOM imports applied to each module by the dependency management plugin, for example for Netty or Reactor Netty. Spring should not export that opinion to its POMs. 2. The exclusion of "org.slf4:jcl-over-slf4j" from *all* dependencies, which made the POMs much larger than necessary and suggested to developers that they should exclude it as well when using all those listed dependencies. In fact, only Apache Tiles currently brings that transitively. This commit removes that information from the POMs. The dependencyManagement Gradle plugin is disabled for POM generation and we manually resolve the dependency versions during the generation phase. The Gradle build is streamlined to exclude "org.slf4:jcl-over-slf4j" only when necessary. Issue: SPR-16893
2018-06-11 21:33:05 +08:00
}
generatedPomCustomization {
enabled = false
}
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
resolutionStrategy {
cacheChangingModulesFor 0, "seconds"
}
repositories {
mavenCentral()
Stop using libs-release This commit makes sure we narrow down dependencies of the Spring Framework to only Maven central. Optional dependencies that are not available on Maven Central are now served from a more specific repository (`libs-spring-framework-build`). Closes gh-23124
2019-09-19 19:27:49 +08:00
maven { url "https://repo.spring.io/libs-spring-framework-build" }
Add repo for transitive dependency on context-propagation Reactor Netty M4 brings in a dependency on context-propagation, so we need the milestone repository. The dependency will become optional for M5, so we only need this temporarily. See gh-28766
2022-07-12 16:54:29 +08:00
maven { url "https://repo.spring.io/milestone" } // temporarily for context-propagation via Reactor Netty
Execute test suite in Gradle using JUnit Platform Closes gh-23286
2019-07-14 01:13:33 +08:00
}
Remove dependency management noise from POMs Prior to this commit, the generated POMs for Spring Framework modules would contain unneeded/harmful information from the Spring Framework build: 1. The BOM imports applied to each module by the dependency management plugin, for example for Netty or Reactor Netty. Spring should not export that opinion to its POMs. 2. The exclusion of "org.slf4:jcl-over-slf4j" from *all* dependencies, which made the POMs much larger than necessary and suggested to developers that they should exclude it as well when using all those listed dependencies. In fact, only Apache Tiles currently brings that transitively. This commit removes that information from the POMs. The dependencyManagement Gradle plugin is disabled for POM generation and we manually resolve the dependency versions during the generation phase. The Gradle build is streamlined to exclude "org.slf4:jcl-over-slf4j" only when necessary. Issue: SPR-16893
2018-06-11 21:33:05 +08:00
}
Disable caching of changing modules and dynamic versions Previously, changing modules (snapshots) and dynamic versions were cached for Gradle's default period of 24 hours and --refresh-dependencies was used to pick up the latest artifacts. This approach has a notable downside. --refresh-dependencies causes all dependencies to be refreshed, irrespective of whether they are expected to change. At a minimum, this results in a HEAD request for every dependency in the build. Running an up-to-date build without --refresh-dependencies takes in the region of 6 seconds: $ ./gradlew build BUILD SUCCESSFUL in 6s 203 actionable tasks: 203 up-to-date The same build with --refresh-dependencies takes almost ten times as long: $ ./gradlew build --refresh-dependencies BUILD SUCCESSFUL in 58s 203 actionable tasks: 203 up-to-date This commit replaces the manual usage of --refresh-dependencies on the command line with a 0 second caching period for changing modules and dynamic versions. This should remove the need to use --refresh-dependencies both locally and on CI, saving almost 1 minute per full build.
2019-09-11 00:12:55 +08:00
configurations.all {
resolutionStrategy {
cacheChangingModulesFor 0, "seconds"
cacheDynamicVersionsFor 0, "seconds"
}
}
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
}
Remove dependency management noise from POMs Prior to this commit, the generated POMs for Spring Framework modules would contain unneeded/harmful information from the Spring Framework build: 1. The BOM imports applied to each module by the dependency management plugin, for example for Netty or Reactor Netty. Spring should not export that opinion to its POMs. 2. The exclusion of "org.slf4:jcl-over-slf4j" from *all* dependencies, which made the POMs much larger than necessary and suggested to developers that they should exclude it as well when using all those listed dependencies. In fact, only Apache Tiles currently brings that transitively. This commit removes that information from the POMs. The dependencyManagement Gradle plugin is disabled for POM generation and we manually resolve the dependency versions during the generation phase. The Gradle build is streamlined to exclude "org.slf4:jcl-over-slf4j" only when necessary. Issue: SPR-16893
2018-06-11 21:33:05 +08:00
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
configure([rootProject] + javaProjects) { project ->
group = "org.springframework"
Improve logging dependencies for tests
2018-01-23 23:42:41 +08:00
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
apply plugin: "java"
Use Gradle test fixture support for spring-core See gh-23550
2019-12-28 18:44:40 +08:00
apply plugin: "java-test-fixtures"
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
apply plugin: "checkstyle"
apply plugin: 'org.springframework.build.compile'
Introduce Gradle Toolchain support in build Prior to this commit, the Spring Framework build would rely on setting a custom Java HOME for building all sources and tests with that JDK. This approach is not flexible enough, since we would be testing the source compatibility against a recent JDK, but not a common case experienced by the community: compiling and running application code with a recent JDK and the official, JDK8-based Framework artifacts. This method is also limiting our choice of JDKs to the ones currently supported by Gradle itself. This commit introduces the support of Gradle JVM Toolchains in the Spring Framework build. We can now select a specific JDK for compiling the main SourceSets (Java, Groovy and Kotlin) and another one for compiling and running the test SourceSets: `./gradlew check -PmainToolChain=8 -PtestToolchain=15` Gradle will automatically find the JDKs present on the host or download one automcatically. You can find out about the ones installed on your host using: `./gradlew -q javaToolchains` Finally, this commit also refactors the CI infrastructure to: * only have a single CI image (with all the supported JDKs) * use this new feature to compile with JDK8 but test it against JDK11 and JDK15. Closes gh-25787
2021-03-12 23:13:50 +08:00
apply from: "${rootDir}/gradle/toolchains.gradle"
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
apply from: "${rootDir}/gradle/ide.gradle"
Update build for spring-web-reactive module
2016-07-14 05:38:47 +08:00
Revert "Revert "Refactor Gradle tasks in Spring Framework build"" This reverts commit fb0d618751a073c067c41266b9601094ccaa7560.
2019-08-21 02:26:43 +08:00
pluginManager.withPlugin("kotlin") {
apply plugin: "org.jetbrains.dokka"
Update dokka to 1.5.0 See gh-26870
2020-09-13 01:41:08 +08:00
apply from: "${rootDir}/gradle/docs-dokka.gradle"
Revert "Revert "Refactor Gradle tasks in Spring Framework build"" This reverts commit fb0d618751a073c067c41266b9601094ccaa7560.
2019-08-21 02:26:43 +08:00
compileKotlin {
kotlinOptions {
Set Kotlin language version to 1.7 Closes gh-28625
2022-06-15 16:01:03 +08:00
languageVersion = "1.7"
apiVersion = "1.7"
Upgrade to Kotlin 1.6.20-M1 This commit upgrades the Kotlin dependencies to 1.6.20-M1 and configures the build to generate Java 17 bytecode for Kotlin classes. Closes gh-27814
2022-02-11 18:39:32 +08:00
freeCompilerArgs = ["-Xjsr305=strict", "-Xsuppress-version-warnings", "-opt-in=kotlin.RequiresOptIn"]
Treat Kotlin warnings as errors Closes gh-23566
2019-09-02 22:49:31 +08:00
allWarningsAsErrors = true
Revert "Revert "Refactor Gradle tasks in Spring Framework build"" This reverts commit fb0d618751a073c067c41266b9601094ccaa7560.
2019-08-21 02:26:43 +08:00
}
Consistently use double quotes (even if no interpolation needed) Includes upgrade to Hibernate ORM 5.3.5, EclipseLink 2.7.3, Selenium HtmlUnit Driver 2.32.1, Jetty 9.4.12 RC2.
2018-08-16 21:32:44 +08:00
}
Revert "Revert "Refactor Gradle tasks in Spring Framework build"" This reverts commit fb0d618751a073c067c41266b9601094ccaa7560.
2019-08-21 02:26:43 +08:00
compileTestKotlin {
kotlinOptions {
Upgrade to Kotlin 1.6.20-M1 This commit upgrades the Kotlin dependencies to 1.6.20-M1 and configures the build to generate Java 17 bytecode for Kotlin classes. Closes gh-27814
2022-02-11 18:39:32 +08:00
freeCompilerArgs = ["-Xjsr305=strict", "-opt-in=kotlin.RequiresOptIn"]
Revert "Revert "Refactor Gradle tasks in Spring Framework build"" This reverts commit fb0d618751a073c067c41266b9601094ccaa7560.
2019-08-21 02:26:43 +08:00
}
Consistently use double quotes (even if no interpolation needed) Includes upgrade to Hibernate ORM 5.3.5, EclipseLink 2.7.3, Selenium HtmlUnit Driver 2.32.1, Jetty 9.4.12 RC2.
2018-08-16 21:32:44 +08:00
}
Groovy-based bean definitions Formerly known as the Grails BeanBuilder, now in Spring proper. Based on https://github.com/spring-projects/spring-framework/pull/355 but heavily refactored and restructured. Issue: SPR-7123
2013-10-18 01:24:08 +08:00
}
Polish build.gradle - Consolidate shared test systemProperty declarations - Consolidate easymock dependency declarations
2013-01-03 19:12:08 +08:00
test {
Simplify Gradle test task configuration
2019-09-03 23:08:45 +08:00
useJUnitPlatform()
include(["**/*Tests.class", "**/*Test.class"])
Consistently use double quotes (even if no interpolation needed) Includes upgrade to Hibernate ORM 5.3.5, EclipseLink 2.7.3, Selenium HtmlUnit Driver 2.32.1, Jetty 9.4.12 RC2.
2018-08-16 21:32:44 +08:00
systemProperty("java.awt.headless", "true")
systemProperty("testGroups", project.properties.get("testGroups"))
Enable io.netty.leakDetection.level=paranoid in tests Issue: SPR-17574
2018-12-13 00:35:50 +08:00
systemProperty("io.netty.leakDetection.level", "paranoid")
Polish build.gradle - Consolidate shared test systemProperty declarations - Consolidate easymock dependency declarations
2013-01-03 19:12:08 +08:00
}
Introduce Gradle-based build - Use recent Gradle 1.0-milestone-8 snapshot - Add initial cut of build.gradle able to compile/test all modules - Update .gitignore - Generate Gradle wrapper scripts - Remove all Eclipse metadata files - Temporarily @Ignore tests that do not pass under Gradle
2011-12-15 08:56:31 +08:00
Consistently use double quotes (even if no interpolation needed) Includes upgrade to Hibernate ORM 5.3.5, EclipseLink 2.7.3, Selenium HtmlUnit Driver 2.32.1, Jetty 9.4.12 RC2.
2018-08-16 21:32:44 +08:00
checkstyle {
Upgrade to R2DBC 1.0 Includes Reactor 2022.0.0-M4, Netty 4.1.79, Jetty 11.0.11, Undertow 2.2.18, Hibernate ORM 5.6.10, Checkstyle 10.3.1 Closes gh-28787
2022-07-13 16:23:51 +08:00
toolVersion = "10.3.1"
Upgrade to Gradle 6.4 Closes gh-25020
2020-05-06 20:25:41 +08:00
configDirectory.set(rootProject.file("src/checkstyle"))
Consistently use double quotes (even if no interpolation needed) Includes upgrade to Hibernate ORM 5.3.5, EclipseLink 2.7.3, Selenium HtmlUnit Driver 2.32.1, Jetty 9.4.12 RC2.
2018-08-16 21:32:44 +08:00
}
Polish .gradle file formatting to use tabs Replace spaces with tabs for consistency with Java source code
2012-12-07 04:56:24 +08:00
dependencies {
Upgrade to Gradle 7.2 This commit upgrades Gradle to 7.2. Gradle configuration names are updated accordingly. This also upgrades Gradle build plugins. See gh-26870
2021-05-22 03:16:30 +08:00
testImplementation("org.junit.jupiter:junit-jupiter-api")
testImplementation("org.junit.jupiter:junit-jupiter-params")
Upgrade to JUnit 5.8 Closes gh-27392
2021-09-06 22:38:37 +08:00
testImplementation("org.junit.platform:junit-platform-suite-api")
Upgrade to Gradle 7.2 This commit upgrades Gradle to 7.2. Gradle configuration names are updated accordingly. This also upgrades Gradle build plugins. See gh-26870
2021-05-22 03:16:30 +08:00
testImplementation("org.mockito:mockito-core")
testImplementation("org.mockito:mockito-junit-jupiter")
testImplementation("io.mockk:mockk")
testImplementation("org.assertj:assertj-core")
Migrate test suite from JUnit 4 to JUnit Jupiter This first commit for this issue: - allows JUnit Jupiter to be used for all tests - adds a dependency on mockito-junit-jupiter - migrates tests in spring-core to JUnit Jupiter, except parameterized tests The following script was developed in order to semi-automate the migration process. https://github.com/sbrannen/junit-converters/blob/master/junit4ToJUnitJupiter.zsh See gh-23451
2019-08-12 17:32:26 +08:00
// Pull in the latest JUnit 5 Launcher API to ensure proper support in IDEs.
Upgrade to Gradle 7.2 This commit upgrades Gradle to 7.2. Gradle configuration names are updated accordingly. This also upgrades Gradle build plugins. See gh-26870
2021-05-22 03:16:30 +08:00
testRuntimeOnly("org.junit.jupiter:junit-jupiter-engine")
Upgrade to R2DBC Arabba-SR11, Kotlin 1.5.32, Jackson 2.12.6
2021-12-16 00:58:59 +08:00
testRuntimeOnly("org.junit.platform:junit-platform-launcher")
Upgrade to JUnit 5.8 Closes gh-27392
2021-09-06 22:38:37 +08:00
testRuntimeOnly("org.junit.platform:junit-platform-suite-engine")
Upgrade to Gradle 7.2 This commit upgrades Gradle to 7.2. Gradle configuration names are updated accordingly. This also upgrades Gradle build plugins. See gh-26870
2021-05-22 03:16:30 +08:00
testRuntimeOnly("org.apache.logging.log4j:log4j-core")
testRuntimeOnly("org.apache.logging.log4j:log4j-jul")
Upgrade to R2DBC Arabba-SR11, Kotlin 1.5.32, Jackson 2.12.6
2021-12-16 00:58:59 +08:00
testRuntimeOnly("org.apache.logging.log4j:log4j-slf4j-impl")
Add checkstyle to build Add checkstyle to the build to enforce Spring Framework coding conventions. Rule suppressions are used for several classes where relaxing the rules makes more sense than fixing them. Issue: SPR-16968
2018-06-14 02:02:02 +08:00
// JSR-305 only used for non-required meta-annotations
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
compileOnly("com.google.code.findbugs:jsr305")
testCompileOnly("com.google.code.findbugs:jsr305")
Upgrade to spring javaformat 0.0.31
2022-02-03 15:49:16 +08:00
checkstyle("io.spring.javaformat:spring-javaformat-checkstyle:0.0.31")
Polish .gradle file formatting to use tabs Replace spaces with tabs for consistency with Java source code
2012-12-07 04:56:24 +08:00
}
Eliminate all Javadoc warnings - Support external Javadoc links using Gradle's javadoc.options.links - Fix all other Javadoc warnings, such as typos, references to non-existent (or no longer existent) types and members, etc, including changes related to the Quartz 2.0 upgrade (SPR-8275) and adding the HTTP PATCH method (SPR-7985). - Suppress all output for project-level `javadoc` tasks in order to hide false-negative warnings about cross-module @see and @link references (e.g. spring-core having a @see reference to spring-web). Use the `--info` (-i) flag to gradle at any time to see project-level javadoc warnings without running the entire `api` task. e.g. `gradle :spring-core:javadoc -i` - Favor root project level `api` task for detection of legitimate Javadoc warnings. There are now zero Javadoc warnings across the entirety of spring-framework. Goal: keep it that way. - Remove all @link and @see references to types and members that exist only in Servlet <= 2.5 and Hibernate <= 4.0, favoring 3.0+ and 4.0+ respectively. This is necessary because only one version of each of these dependencies can be present on the global `api` javadoc task's classpath. To that end, the `api` task classpath has now been customized to ensure that the Servlet 3 API and Hibernate Core 4 jars have precedence. - SPR-8896 replaced our dependency on aspectjrt with a dependency on aspectjweaver, which is fine from a POM point of view, but causes a spurious warning to be emitted from the ant iajc task that it "cannot find aspectjrt on the classpath" - even though aspectjweaver is perfectly sufficient. In the name of keeping the console quiet, a new `rt` configuration has been added, and aspectjrt added as a dependency to it. In turn, configurations.rt.asPath is appended to the iajc classpath during both compileJava and compileTestJava for spring-aspects. Issue: SPR-10078, SPR-8275, SPR-7985, SPR-8896
2012-12-11 18:56:38 +08:00
ext.javadocLinks = [
Upgrade Javadoc URLs for JDK 17 based build Prior to this commit, the Javadoc task would fail on `spring-context-indexer` and `spring-instrumentation`. It seems that missing remote docs or HTTP redirects were failing the process. This commit removes the missing published Javadocs and updates the version for the JDK API. See gh-17778
2021-09-16 00:45:15 +08:00
"https://docs.oracle.com/en/java/javase/17/docs/api/",
Link to Jakarta EE APIs instead of Java EE APIs
2021-09-29 23:19:19 +08:00
"https://jakarta.ee/specifications/platform/9/apidocs/",
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
"https://docs.oracle.com/cd/E13222_01/wls/docs90/javadocs/", // CommonJ
Upgrade to Gradle 7.2 This commit upgrades Gradle to 7.2. Gradle configuration names are updated accordingly. This also upgrades Gradle build plugins. See gh-26870
2021-05-22 03:16:30 +08:00
"https://www.ibm.com/docs/api/v1/content/SSEQTP_8.5.5/com.ibm.websphere.javadoc.doc/web/apidocs/",
Reintroduce references to JBoss AS Javadoc Closes gh-27860
2022-01-10 17:10:59 +08:00
"https://docs.jboss.org/jbossas/javadoc/4.0.5/connector/",
"https://docs.jboss.org/jbossas/javadoc/7.1.2.Final/",
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
"https://www.eclipse.org/aspectj/doc/released/aspectj5rt-api/",
"https://www.quartz-scheduler.org/api/2.3.0/",
Upgrade to Jackson 2.10.0 Closes gh-23662
2019-09-28 04:38:27 +08:00
"https://fasterxml.github.io/jackson-core/javadoc/2.10/",
"https://fasterxml.github.io/jackson-databind/javadoc/2.10/",
"https://fasterxml.github.io/jackson-dataformat-xml/javadoc/2.10/",
Reintroduce Javadoc links to Apache HttpClient 5.1 APIs See gh-28842
2022-07-19 20:23:22 +08:00
"https://hc.apache.org/httpcomponents-client-5.1.x/current/httpclient5/apidocs/",
Fix issues in Javadoc
2020-10-27 18:05:31 +08:00
"https://projectreactor.io/docs/test/release/api/",
Upgrade to JUnit 4.13.2 Closes gh-26543
2021-02-14 02:22:16 +08:00
"https://junit.org/junit4/javadoc/4.13.2/",
Merge branch '5.3.x'
2021-09-29 22:56:33 +08:00
// TODO Uncomment link to JUnit 5 docs once we have sorted out
// the following warning in the build.
//
Upgrade to JUnit 5.9 Closes gh-28752
2022-07-27 16:02:34 +08:00
// warning: The code being documented uses packages in the unnamed module, but the packages defined in https://junit.org/junit5/docs/5.9.0/api/ are in named modules.
Merge branch '5.3.x'
2021-09-29 22:56:33 +08:00
//
Upgrade to JUnit 5.9 Closes gh-28752
2022-07-27 16:02:34 +08:00
// "https://junit.org/junit5/docs/5.9.0/api/",
Polish Gradle upgrade Closes gh-26870
2021-09-13 15:36:07 +08:00
"https://www.reactive-streams.org/reactive-streams-1.0.3-javadoc/",
"https://javadoc.io/static/io.rsocket/rsocket-core/1.1.1/",
Upgrade to R2DBC 1.0 Includes Reactor 2022.0.0-M4, Netty 4.1.79, Jetty 11.0.11, Undertow 2.2.18, Hibernate ORM 5.6.10, Checkstyle 10.3.1 Closes gh-28787
2022-07-13 16:23:51 +08:00
"https://r2dbc.io/spec/1.0.0.RELEASE/api/",
Fix Javadoc links to JSR 305 annotations where feasible Prior to this commit, we only (indirectly) configured external Javadoc links for types in the javax.annotation package for JSR 250, since those types are part of Java 8 SE. However, an external Javadoc link for types from JSR 305 was not configured. To address this issue, this commit now configures an external Javadoc link for JSR 305 types. However, the external Javadoc link for JSR 305 must be configured last to ensure that types from JSR 250 (such as @PostConstruct) are still supported. This is due to the fact that JSR 250 and JSR 305 both define types in javax.annotation, which results in a split package, and the javadoc tool does not support split packages across multiple external Javadoc sites. Instead, the Javadoc tool iterates over all external links, and the first external site that claims to support a given package (via the package-list file) wins. This means: - Javadoc for JSR 250 annotations is fully supported. - Javadoc for JSR 305 annotations in the javax.annotation package will continue to result in a 404 (page not found) error. - Javadoc for JSR 305 annotations in the javax.annotation.meta package is fully supported. For Spring Framework 6.0, the Javadoc for JSR 250 types in jakarta.annotation package is served from the JBoss Application Server Javadoc site instead of from Oracle's Java SE documentation site, since JSR 250 annotations are no longer included in Java SE. Closes gh-27904
2022-01-21 22:52:09 +08:00
// The external Javadoc link for JSR 305 must come last to ensure that types from
// JSR 250 (such as @PostConstruct) are still supported. This is due to the fact
// that JSR 250 and JSR 305 both define types in javax.annotation, which results
// in a split package, and the javadoc tool does not support split packages
// across multiple external Javadoc sites.
"https://www.javadoc.io/doc/com.google.code.findbugs/jsr305/3.0.2/"
Eliminate all Javadoc warnings - Support external Javadoc links using Gradle's javadoc.options.links - Fix all other Javadoc warnings, such as typos, references to non-existent (or no longer existent) types and members, etc, including changes related to the Quartz 2.0 upgrade (SPR-8275) and adding the HTTP PATCH method (SPR-7985). - Suppress all output for project-level `javadoc` tasks in order to hide false-negative warnings about cross-module @see and @link references (e.g. spring-core having a @see reference to spring-web). Use the `--info` (-i) flag to gradle at any time to see project-level javadoc warnings without running the entire `api` task. e.g. `gradle :spring-core:javadoc -i` - Favor root project level `api` task for detection of legitimate Javadoc warnings. There are now zero Javadoc warnings across the entirety of spring-framework. Goal: keep it that way. - Remove all @link and @see references to types and members that exist only in Servlet <= 2.5 and Hibernate <= 4.0, favoring 3.0+ and 4.0+ respectively. This is necessary because only one version of each of these dependencies can be present on the global `api` javadoc task's classpath. To that end, the `api` task classpath has now been customized to ensure that the Servlet 3 API and Hibernate Core 4 jars have precedence. - SPR-8896 replaced our dependency on aspectjrt with a dependency on aspectjweaver, which is fine from a POM point of view, but causes a spurious warning to be emitted from the ant iajc task that it "cannot find aspectjrt on the classpath" - even though aspectjweaver is perfectly sufficient. In the name of keeping the console quiet, a new `rt` configuration has been added, and aspectjrt added as a dependency to it. In turn, configurations.rt.asPath is appended to the iajc classpath during both compileJava and compileTestJava for spring-aspects. Issue: SPR-10078, SPR-8275, SPR-7985, SPR-8896
2012-12-11 18:56:38 +08:00
] as String[]
Upgrade to JUnit 4.11 snapshot in support of JDK7 Class#getDeclaredMembers returns arbitrary results under JDK7. This results in non-deterministic execution of JUnit test methods, often revealing unintended dependencies between methods that rely on a specific order to succeed. JUnit 4.11 contains support for predictable test ordering [1], but at the time of this commit, JUnit 4.11 has not yet been released. Therefore we are testing against a snapshot version [2], which has been uploaded to repo.springsource.org [3] for easy access. Note that this artifact may be removed when JUnit 4.11 goes GA. - Care has been taken to ensure that spring-test's compile-time dependency on JUnit remains at 4.10. This means that the spring-test pom.xml will continue to have an optional <dependency> on JUnit 4.10, instead of the 4.11 snapshot. - For reasons not fully understood, the upgrade to the 4.11 snapshot of junit-dep caused NoSuchMethodErrors around certain Hamcrest types, particularly CoreMatchers and Matchers. import statements have been updated accordingly throughout affected test cases. - Runtime errors also occurred around uses of JUnit @Rule and ExpectedException. These have been reverted to use simpler mechanisms like @Test(expected) in the meantime. - Some test methods with order-based dependencies on one another have been renamed in order to fall in line with JUnit 4.11's new method ordering (as opposed to actually fixing the inter-test dependencies). In other areas, the fix was as simple as adding a tearDown method and cleaning up state. - For no apparent reason, the timeout in AspectJAutoProxyCreatorTests' testAspectsAndAdvisorNotAppliedToPrototypeIsFastEnough method begins to be exceeded. Prior to this commit the timeout value was 3000 ms; on the CI server under Linux/JDK6 and JDK7, the test begins taking anywhere from 3500-5500 ms with this commit. It is presumed that this is an incidental artifact of the upgrade to JUnit 4.11. In any case, there are no changes to src/main in this commit, so this should not actually represent a performance risk for Spring Framework users. The timeout has been increased to 6000 ms to accommodate this situation. [1]: https://github.com/KentBeck/junit/pull/293 [2]: https://github.com/downloads/KentBeck/junit/junit-dep-4.11-SNAPSHOT-20120805-1225.jar [3]: https://repo.springsource.org/simple/ext-release-local/junit/junit-dep/4.11.20120805.1225 Issue: SPR-9783
2012-09-10 03:41:39 +08:00
}
Revert "Revert "Refactor Gradle tasks in Spring Framework build"" This reverts commit fb0d618751a073c067c41266b9601094ccaa7560.
2019-08-21 02:26:43 +08:00
configure(moduleProjects) { project ->
apply from: "${rootDir}/gradle/spring-module.gradle"
Introduce Gradle-based build - Use recent Gradle 1.0-milestone-8 snapshot - Add initial cut of build.gradle able to compile/test all modules - Update .gitignore - Generate Gradle wrapper scripts - Remove all Eclipse metadata files - Temporarily @Ignore tests that do not pass under Gradle
2011-12-15 08:56:31 +08:00
}
Generate -docs, -schema and -dist zips - Add 'api' gradle task to generate project-wide API Javadoc results in <root>/build/api - Add docsZip task including api and reference documentation suitable for publication to http://static.springframework.org/docs/spring-framework - Add schemaZip task including all spring-* XSD files suitable for publication to http://static.springframework.org/schema - Add distZip task to include all libs, docs and schema - filter src/dist/*.txt for ${copyright} and ${version} - copy legal (notice, license) dynamically into individual jar files - copy legal and readme files into root of distribution zip - Refactor location of 'wrapper' task Each of the zip tasks (docsZip, schemaZip, distZip) have been added to the 'archives' configuration, meaning that (a) they will be built automatically with `gradle build` and (b) will be published automatically to artifactory when using the Artifactory Gradle plugin and/or Artifactory Bamboo integration.
2012-01-17 05:28:06 +08:00
configure(rootProject) {
Consistently use double quotes (even if no interpolation needed) Includes upgrade to Hibernate ORM 5.3.5, EclipseLink 2.7.3, Selenium HtmlUnit Driver 2.32.1, Jetty 9.4.12 RC2.
2018-08-16 21:32:44 +08:00
description = "Spring Framework"
Polish .gradle file formatting to use tabs Replace spaces with tabs for consistency with Java source code
2012-12-07 04:56:24 +08:00
Revert "Revert "Refactor Gradle tasks in Spring Framework build"" This reverts commit fb0d618751a073c067c41266b9601094ccaa7560.
2019-08-21 02:26:43 +08:00
apply plugin: "kotlin"
Add nohttp to build See gh-22839
2019-04-29 23:47:05 +08:00
apply plugin: "io.spring.nohttp"
Use JApiCmp Gradle plugin for API diffs This commit removes JDiff from the Spring Framework build and instead, adds a Gradle plugin that configure JApiCmp tasks on the framework modules. Fixes gh-22942 See gh-23282
2019-08-19 16:15:43 +08:00
apply plugin: 'org.springframework.build.api-diff'
Configure Maven publications with Gradle Prior to this commit, the build would use a custom task to create a BOM and manually include/exclude/customize dependencies. It would also use the "maven" plugin to customize the POM before publication. This commit now uses a Gradle Java Platform for publishing the Spring Framework BOM. We're also now using the "maven-publish" plugin to prepare and customize publications. This commit also tells the artifactory plugin (which is currently applied only on the CI) not to publish internal modules. See gh-23282
2019-08-21 21:24:03 +08:00
apply from: "${rootDir}/gradle/publications.gradle"
Revert "Revert "Refactor Gradle tasks in Spring Framework build"" This reverts commit fb0d618751a073c067c41266b9601094ccaa7560.
2019-08-21 02:26:43 +08:00
apply from: "${rootDir}/gradle/docs.gradle"
Polish .gradle file formatting to use tabs Replace spaces with tabs for consistency with Java source code
2012-12-07 04:56:24 +08:00
Add nohttp to build See gh-22839
2019-04-29 23:47:05 +08:00
nohttp {
source.exclude "**/test-output/**"
Upgrade to nohttp 0.0.5 Closes gh-25266
2020-06-17 20:46:23 +08:00
allowlistFile = project.file("src/nohttp/allowlist.lines")
Improve exclusions of checkstyleNoHttp task This commit adds the following exclusions to the source of the checkstyleNoHttp tasks for each project in the build and for buildSrc: - bin/ directory (created by Eclipse Buildship) - .settings directory (created by Eclipse) - .classpath file (created by Eclipse) - .project file (created by Eclipse) An exclusion for the build/ directory is also configured as the NoHttp plugin does not exclude it by default for buildSrc. Closes gh-23702
2019-09-25 21:29:19 +08:00
def rootPath = file(rootDir).toPath()
def projectDirs = allprojects.collect { it.projectDir } + "${rootDir}/buildSrc"
projectDirs.forEach { dir ->
[ 'bin', 'build', 'out', '.settings' ]
.collect { rootPath.relativize(new File(dir, it).toPath()) }
.forEach { source.exclude "$it/**" }
[ '.classpath', '.project' ]
.collect { rootPath.relativize(new File(dir, it).toPath()) }
.forEach { source.exclude "$it" }
Add nohttp to build See gh-22839
2019-04-29 23:47:05 +08:00
}
}
Configure Maven publications with Gradle Prior to this commit, the build would use a custom task to create a BOM and manually include/exclude/customize dependencies. It would also use the "maven" plugin to customize the POM before publication. This commit now uses a Gradle Java Platform for publishing the Spring Framework BOM. We're also now using the "maven-publish" plugin to prepare and customize publications. This commit also tells the artifactory plugin (which is currently applied only on the CI) not to publish internal modules. See gh-23282
2019-08-21 21:24:03 +08:00
publishing {
publications {
Change Gradle publication name for artifactory This commit switches to the default publication name considered by the artifactory plugin when it comes to publishing artifacts to the artifactory repository. See gh-23282
2019-08-22 00:42:17 +08:00
mavenJava(MavenPublication) {
Configure Maven publications with Gradle Prior to this commit, the build would use a custom task to create a BOM and manually include/exclude/customize dependencies. It would also use the "maven" plugin to customize the POM before publication. This commit now uses a Gradle Java Platform for publishing the Spring Framework BOM. We're also now using the "maven-publish" plugin to prepare and customize publications. This commit also tells the artifactory plugin (which is currently applied only on the CI) not to publish internal modules. See gh-23282
2019-08-21 21:24:03 +08:00
artifact docsZip
artifact schemaZip
artifact distZip
}
}
Polish .gradle file formatting to use tabs Replace spaces with tabs for consistency with Java source code
2012-12-07 04:56:24 +08:00
}
Remove need to manually set wrapper GRADLE_OPTS Replace the wrapper task with a variant that automatically adds the appropriate GRADLE_OPTS to the shell and bat files.
2012-11-01 08:29:00 +08:00
}