eec183ef28
Prior to this commit, the three `test` tasks in the spring-test module shared the same output directory for test reports. This had the negative side effect of causing Gradle to believe that the tasks were not UP-TO-DATE. Consequently, all three `test` tasks in the spring-test module were executed for every build even if there were zero changes in the spring-test module. This commit fixes this issue by allowing Gradle to use the default test results output directory for each `test` task. Thanks to @marcphilipp for providing the tip. In addition, the Artifactory Gradle task in the Default Job of the Bamboo build plan for the Spring Framework (SPR-PUB) has been updated to use the following custom test results directory pattern: `**/build/test-results/**/*.xml`. See: https://guides.gradle.org/using-build-cache/#concepts_overlapping_outputs |
||
|---|---|---|
| .github | ||
| buildSrc | ||
| gradle | ||
| spring-aop | ||
| spring-aspects | ||
| spring-beans | ||
| spring-context | ||
| spring-context-indexer | ||
| spring-context-support | ||
| spring-core | ||
| spring-core-coroutines | ||
| spring-expression | ||
| spring-framework-bom | ||
| spring-instrument | ||
| spring-jcl | ||
| spring-jdbc | ||
| spring-jms | ||
| spring-messaging | ||
| spring-orm | ||
| spring-oxm | ||
| spring-test | ||
| spring-tx | ||
| spring-web | ||
| spring-webflux | ||
| spring-webmvc | ||
| spring-websocket | ||
| src | ||
| .editorconfig | ||
| .gitignore | ||
| .mailmap | ||
| CODE_OF_CONDUCT.adoc | ||
| CONTRIBUTING.md | ||
| README.md | ||
| build.gradle | ||
| gradle.properties | ||
| gradlew | ||
| gradlew.bat | ||
| import-into-eclipse.md | ||
| import-into-idea.md | ||
| settings.gradle | ||
README.md
Spring Framework
This is the home of the Spring Framework: the foundation for all Spring projects. Collectively the Spring Framework and the family of Spring projects is often referred to simply as "Spring".
Spring provides everything required beyond the Java programming language for creating enterprise applications for a wide range of scenarios and architectures. Please read the Overview section as reference for a more complete introduction.
Code of Conduct
This project is governed by the Spring Code of Conduct. By participating, you are expected to uphold this code of conduct. Please report unacceptable behavior to spring-code-of-conduct@pivotal.io.
Access to Binaries
For access to artifacts or a distribution zip, see the Spring Framework Artifacts wiki page.
Documentation
The Spring Framework maintains reference documentation (published and source), Github wiki pages, and an API reference. There are also guides and tutorials across Spring projects.
Build from Source
See the Build from Source Wiki page and the CONTRIBUTING.md file.
Stay in Touch
Follow @SpringCentral, @SpringFramework, and its team members on Twitter. In-depth articles can be found at The Spring Blog, and releases are announced via our news feed.
License
The Spring Framework is released under version 2.0 of the Apache License.