tchekai704
/
src-spring-framework
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
Spring Framework
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
26292 Commits
19 Branches
274 Tags
318 MiB
Tree: c20efba45c
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'c20efba45c'
${ noResults }
src-spring-framework/build.gradle

178 lines
6.7 KiB
Raw Normal View History Unescape

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
9 years ago
plugins {
Upgrade to nohttp 0.0.11
2 years ago
id 'io.spring.nohttp' version '0.0.11'
Upgrade Gradle plugins
2 years ago
id 'io.freefair.aspectj' version '6.5.0.3' apply false
Move Kotlin Gradle build config to convention This commit moves the Kotlin build configuration from the Gradle DSL to a dedicated convention in buildSrc.
2 years ago
// kotlinVersion is managed in gradle.properties
id 'org.jetbrains.kotlin.plugin.serialization' version "${kotlinVersion}" apply false
Create framework-docs module This commit creates a new "framework-docs" module, which is dedicated to documentation generation (reference and API docs). This commit refactors the build configuration and moves the asciidoc files to a separate location, but does not change the name nor the nature of published artifacts. Closes gh-29417
2 years ago
id 'org.jetbrains.dokka' version '1.7.20'
id 'org.asciidoctor.jvm.convert' version '3.3.2' apply false
id 'org.asciidoctor.jvm.pdf' version '3.3.2' apply false
Upgrade Gradle plugins
2 years ago
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'
Upgrade JMH build plugins This commit upgrades the Gradle JMH plugin to 0.6.8 and the companion JMH version to 1.36.
2 years ago
id 'me.champeau.jmh' version '0.6.8' 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
7 years ago
}
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
11 years ago
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
5 years ago
moduleProjects = subprojects.findAll { it.name.startsWith("spring-") }
Replace dependency management plugin with built-in platform support
2 years ago
javaProjects = subprojects - project(":framework-bom") - project(":framework-platform")
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
11 years ago
}
Fix missing findbugs dependency for Dokka task
5 years ago
configure(allprojects) { project ->
Replace dependency management plugin with built-in platform support
2 years ago
repositories {
mavenCentral()
Add milestone repo for optional Netty 5 support Closes gh-29498
2 years ago
maven {
url "https://repo.spring.io/milestone"
content {
// Netty 5 optional support
includeGroup 'io.projectreactor.netty'
}
}
Replace dependency management plugin with built-in platform support
2 years ago
maven { url "https://repo.spring.io/libs-spring-framework-build" }
Add Micrometer BOM 1.10 dependency management This new BOM dependency is necessary, as Spring Framework will implement direct instrumentation with Micrometer as a mandatory or optional dependency in several modules.
2 years ago
if (version.contains('-')) {
maven { url "https://repo.spring.io/milestone" }
}
if (version.endsWith('-SNAPSHOT')) {
maven { url "https://repo.spring.io/snapshot" }
}
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
7 years ago
}
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.
5 years ago
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
5 years ago
}
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
7 years ago
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
5 years ago
configure([rootProject] + javaProjects) { project ->
group = "org.springframework"
Improve logging dependencies for tests
7 years ago
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
5 years ago
apply plugin: "java"
Use Gradle test fixture support for spring-core See gh-23550
5 years ago
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
5 years ago
apply plugin: "checkstyle"
Apply Gradle Test Retry plugin The plugin is configured to detect flaky tests and retry them 3 times when running on the CI, but still reports failures. This will provide a standard way to detect flaky tests as failures and successful attempts are shown in the tests report.
2 years ago
apply plugin: 'org.springframework.build.conventions'
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
4 years ago
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
5 years ago
apply from: "${rootDir}/gradle/ide.gradle"
Update build for spring-web-reactive module
8 years ago
Replace dependency management plugin with built-in platform support
2 years ago
configurations {
dependencyManagement {
canBeConsumed = false
canBeResolved = false
visible = false
}
matching { it.name.endsWith("Classpath") }.all { it.extendsFrom(dependencyManagement) }
}
Polish build.gradle - Consolidate shared test systemProperty declarations - Consolidate easymock dependency declarations
12 years ago
test {
Simplify Gradle test task configuration
5 years ago
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.
6 years ago
systemProperty("java.awt.headless", "true")
systemProperty("testGroups", project.properties.get("testGroups"))
Enable io.netty.leakDetection.level=paranoid in tests Issue: SPR-17574
6 years ago
systemProperty("io.netty.leakDetection.level", "paranoid")
Enable leak detection in Netty 5 tests See gh-29310
2 years ago
systemProperty("io.netty5.leakDetectionLevel", "paranoid")
systemProperty("io.netty5.leakDetection.targetRecords", "32")
systemProperty("io.netty5.buffer.lifecycleTracingEnabled", "true")
systemProperty("io.netty5.buffer.leakDetectionEnabled", "true")
Add opens for Gradle test workers After our upgrade to Gradle 7.5.1, our test suite requires changes to our test configuration. See: https://docs.gradle.org/7.5/userguide/upgrading_version_7.html#removes_implicit_add_opens_for_test_workers
2 years ago
jvmArgs(["--add-opens=java.base/java.lang=ALL-UNNAMED",
"--add-opens=java.base/java.util=ALL-UNNAMED"])
Polish build.gradle - Consolidate shared test systemProperty declarations - Consolidate easymock dependency declarations
12 years ago
}
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
13 years ago
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.
6 years ago
checkstyle {
Upgrade to Groovy 4.0.8, Tomcat 10.1.5, Netty 4.1.87, Undertow 2.3.3, Jackson 2.14.2, Woodstox 6.5, Mockito 5.1.1, AssertJ 3.24.2, HtmlUnit 2.70, Checkstyle 10.7
2 years ago
toolVersion = "10.7.0"
Upgrade to Gradle 6.4 Closes gh-25020
5 years ago
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.
6 years ago
}
Allocate more memory to Checkstyle tasks
2 years ago
tasks.named("checkstyleMain").configure {
maxHeapSize = "1g"
}
tasks.named("checkstyleTest").configure {
maxHeapSize = "1g"
}
Polish .gradle file formatting to use tabs Replace spaces with tabs for consistency with Java source code
12 years ago
dependencies {
Replace dependency management plugin with built-in platform support
2 years ago
dependencyManagement(enforcedPlatform(dependencies.project(path: ":framework-platform")))
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
4 years ago
testImplementation("org.junit.jupiter:junit-jupiter-api")
testImplementation("org.junit.jupiter:junit-jupiter-params")
Upgrade to JUnit 5.8 Closes gh-27392
3 years ago
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
4 years ago
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
5 years ago
// 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
4 years ago
testRuntimeOnly("org.junit.jupiter:junit-jupiter-engine")
Upgrade to R2DBC Arabba-SR11, Kotlin 1.5.32, Jackson 2.12.6
3 years ago
testRuntimeOnly("org.junit.platform:junit-platform-launcher")
Upgrade to JUnit 5.8 Closes gh-27392
3 years ago
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
4 years ago
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
3 years ago
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
7 years ago
// 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
5 years ago
compileOnly("com.google.code.findbugs:jsr305")
testCompileOnly("com.google.code.findbugs:jsr305")
Upgrade to spring javaformat 0.0.31
3 years ago
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
12 years ago
}
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
12 years ago
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
3 years ago
"https://docs.oracle.com/en/java/javase/17/docs/api/",
Link to Jakarta EE APIs instead of Java EE APIs
3 years ago
"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
5 years ago
"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
4 years ago
"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
3 years ago
"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
5 years ago
"https://www.eclipse.org/aspectj/doc/released/aspectj5rt-api/",
"https://www.quartz-scheduler.org/api/2.3.0/",
Fix build due to Jackson Javadoc publication changes The Jackson project no longer publishes Javadoc at https://fasterxml.github.io which breaks the `javadoc` and `api` build tasks due to their dependency on that web site for external Javadoc links. As a workaround, we now reference Jackson's Javadoc via https://www.javadoc.io. See https://github.com/FasterXML/jackson-databind/issues/3440 Closes gh-29894
2 years ago
"https://www.javadoc.io/doc/com.fasterxml.jackson.core/jackson-core/2.14.1/",
"https://www.javadoc.io/doc/com.fasterxml.jackson.core/jackson-databind/2.14.1/",
"https://www.javadoc.io/doc/com.fasterxml.jackson.dataformat/jackson-dataformat-xml/2.14.1/",
Revert "Ignore HttpComponents Javadoc" This reverts commit f50b472ceb6fc2fa25675672bdd0ca422ed8000f. HttpComponents Javadoc is available again. See gh-29479 See https://issues.apache.org/jira/browse/HTTPCLIENT-2227
2 years ago
"https://hc.apache.org/httpcomponents-client-5.2.x/current/httpclient5/apidocs/",
Fix issues in Javadoc
4 years ago
"https://projectreactor.io/docs/test/release/api/",
Upgrade to JUnit 4.13.2 Closes gh-26543
4 years ago
"https://junit.org/junit4/javadoc/4.13.2/",
Merge branch '5.3.x'
3 years ago
// TODO Uncomment link to JUnit 5 docs once we have sorted out
// the following warning in the build.
//
Upgrade to JUnit 5.9.2
2 years ago
// warning: The code being documented uses packages in the unnamed module, but the packages defined in https://junit.org/junit5/docs/5.9.2/api/ are in named modules.
Merge branch '5.3.x'
3 years ago
//
Upgrade to JUnit 5.9.2
2 years ago
// "https://junit.org/junit5/docs/5.9.2/api/",
Polish Gradle upgrade Closes gh-26870
3 years ago
"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
2 years ago
"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
3 years ago
// 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
12 years ago
] 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
12 years ago
}
Revert "Revert "Refactor Gradle tasks in Spring Framework build"" This reverts commit fb0d618751a073c067c41266b9601094ccaa7560.
5 years ago
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
13 years ago
}
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.
13 years ago
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.
6 years ago
description = "Spring Framework"
Polish .gradle file formatting to use tabs Replace spaces with tabs for consistency with Java source code
12 years ago
Add nohttp to build See gh-22839
6 years ago
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
5 years ago
apply plugin: 'org.springframework.build.api-diff'
Polish .gradle file formatting to use tabs Replace spaces with tabs for consistency with Java source code
12 years ago
Add nohttp to build See gh-22839
6 years ago
nohttp {
source.exclude "**/test-output/**"
Upgrade to nohttp 0.0.5 Closes gh-25266
4 years ago
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
5 years ago
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
6 years ago
}
}
Configure more memory for checkstyleNohttp See https://docs.gradle.org/7.5/release-notes.html#checkstyle-tasks-use-toolchains-and-execute-in-parallel-by-default
2 years ago
tasks.named("checkstyleNohttp").configure {
maxHeapSize = "1g"
}
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.
12 years ago
}