Prior to this commit, the Asciidoctor Gradle tasks generated top-level HTML and PDF documents for AsciiDoc files that are included in other top-level documents. This causes slower builds and results in each include-file being published twice: 1) inline in the including document (as intended) 2) as a top-level document but missing surrounding context (unintended) The reason these include-files are generated as top-level documents is that the asciidoctor and asciidoctorPdf Gradle tasks are configured to use '*.adoc' as the input source files. This commit addresses this issue by moving the following include-files to new subdirectories. Locating the include-files in the subdirectories causes them to be ignored in the '*.adoc' pattern used to identify input source files. - data-access-appendix.adoc -> data-access/data-access-appendix.adoc - integration-appendix.adoc -> integration/integration-appendix.adoc - testing-webtestclient.adoc -> testing/testing-webtestclient.adoc Closes gh-25783 |
||
|---|---|---|
| .github | ||
| buildSrc | ||
| framework-bom | ||
| gradle | ||
| integration-tests | ||
| spring-aop | ||
| spring-aspects | ||
| spring-beans | ||
| spring-context | ||
| spring-context-indexer | ||
| spring-context-support | ||
| spring-core | ||
| spring-expression | ||
| 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 | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| CODE_OF_CONDUCT.adoc | ||
| CONTRIBUTING.md | ||
| LICENSE.txt | ||
| README.md | ||
| SECURITY.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 are 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.