Skip to content

Commit 1478d45

Browse files
fyyzkdfyyzkd
committed
upload spring 5.1
0 parents  commit 1478d45

File tree

8,128 files changed

+1252062
-0
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

8,128 files changed

+1252062
-0
lines changed

‎.editorconfig‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
root = true
2+
3+
[*.{adoc,bat,groovy,html,java,js,jsp,kt,kts,md,properties,py,rb,sh,sql,svg,txt,xml,xsd}]
4+
charset = utf-8
5+
6+
[*.{groovy,java,kt,kts,xml,xsd}]
7+
indent_style = tab
8+
indent_size = 4
9+
continuation_indent_size = 8
10+
end_of_line = lf

‎.gitignore‎

Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
*.java.hsp
2+
*.sonarj
3+
*.sw*
4+
.DS_Store
5+
.settings
6+
.springBeans
7+
bin
8+
build.sh
9+
integration-repo
10+
ivy-cache
11+
jxl.log
12+
jmx.log
13+
derby.log
14+
spring-test/test-output/
15+
.gradle
16+
argfile*
17+
pom.xml
18+
activemq-data/
19+
20+
classes/
21+
/build
22+
buildSrc/build
23+
/spring-*/build
24+
/src/asciidoc/build
25+
target/
26+
27+
# Eclipse artifacts, including WTP generated manifests
28+
.classpath
29+
.project
30+
spring-*/src/main/java/META-INF/MANIFEST.MF
31+
32+
# IDEA artifacts and output dirs
33+
*.iml
34+
*.ipr
35+
*.iws
36+
.idea
37+
out
38+
test-output
39+
atlassian-ide-plugin.xml
40+
.gradletasknamecache
41+
/buildSrc/.gradle
42+
/buildSrc/build

‎.mailmap‎

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
Juergen Hoeller <[email protected]> jhoeller <[email protected]>
2+
<[email protected]> <[email protected]>
3+
<[email protected]> <[email protected]>
4+
<[email protected]> <[email protected]>
5+
<[email protected]> <[email protected]>
6+
<[email protected]> <[email protected]>
7+
<[email protected]> <[email protected]>
8+
<[email protected]> <[email protected]>
9+
<[email protected]> <[email protected]>
10+
<[email protected]> <[email protected]>
11+
<[email protected]> <[email protected]>
12+
<[email protected]> <[email protected]>
13+
<[email protected]> <[email protected]>
14+
<[email protected]> <[email protected]>
15+
<[email protected]> <[email protected]>
16+
<[email protected]> <[email protected]>
17+
<[email protected]> <[email protected]>
18+
<[email protected]> <[email protected]>
19+
<[email protected]> <[email protected]>
20+
<[email protected]> <[email protected]>
21+
<[email protected]> <[email protected]>
22+
<[email protected]> <[email protected]>
23+
Nick Williams <[email protected]> Nicholas Williams <[email protected]>

‎CODE_OF_CONDUCT.adoc‎

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
= Contributor Code of Conduct
2+
3+
As contributors and maintainers of this project, and in the interest of fostering an open
4+
and welcoming community, we pledge to respect all people who contribute through reporting
5+
issues, posting feature requests, updating documentation, submitting pull requests or
6+
patches, and other activities.
7+
8+
We are committed to making participation in this project a harassment-free experience for
9+
everyone, regardless of level of experience, gender, gender identity and expression,
10+
sexual orientation, disability, personal appearance, body size, race, ethnicity, age,
11+
religion, or nationality.
12+
13+
Examples of unacceptable behavior by participants include:
14+
15+
* The use of sexualized language or imagery
16+
* Personal attacks
17+
* Trolling or insulting/derogatory comments
18+
* Public or private harassment
19+
* Publishing other's private information, such as physical or electronic addresses,
20+
without explicit permission
21+
* Other unethical or unprofessional conduct
22+
23+
Project maintainers have the right and responsibility to remove, edit, or reject comments,
24+
commits, code, wiki edits, issues, and other contributions that are not aligned to this
25+
Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors
26+
that they deem inappropriate, threatening, offensive, or harmful.
27+
28+
By adopting this Code of Conduct, project maintainers commit themselves to fairly and
29+
consistently applying these principles to every aspect of managing this project. Project
30+
maintainers who do not follow or enforce the Code of Conduct may be permanently removed
31+
from the project team.
32+
33+
This Code of Conduct applies both within project spaces and in public spaces when an
34+
individual is representing the project or its community.
35+
36+
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by
37+
contacting a project maintainer at [email protected] . All complaints will
38+
be reviewed and investigated and will result in a response that is deemed necessary and
39+
appropriate to the circumstances. Maintainers are obligated to maintain confidentiality
40+
with regard to the reporter of an incident.
41+
42+
This Code of Conduct is adapted from the
43+
https://contributor-covenant.org[Contributor Covenant], version 1.3.0, available at
44+
https://contributor-covenant.org/version/1/3/0/[contributor-covenant.org/version/1/3/0/]

‎CONTRIBUTING.md‎

Lines changed: 128 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,128 @@
1+
# Contributing to the Spring Framework
2+
3+
First off, thank you for taking the time to contribute! :+1: :tada:
4+
5+
### Table of Contents
6+
7+
* [Code of Conduct](#code-of-conduct)
8+
* [How to Contribute](#how-to-contribute)
9+
* [Discuss](#discuss)
10+
* [Create a Ticket](#create-a-ticket)
11+
* [Ticket Lifecycle](#ticket-lifecycle)
12+
* [Submit a Pull Request](#submit-a-pull-request)
13+
* [Build from Source](#build-from-source)
14+
* [Source Code Style](#source-code-style)
15+
* [Reference Docs](#reference-docs)
16+
17+
### Code of Conduct
18+
19+
This project is governed by the [Spring Code of Conduct](CODE_OF_CONDUCT.adoc).
20+
By participating you are expected to uphold this code.
21+
Please report unacceptable behavior to [email protected].
22+
23+
### How to Contribute
24+
25+
#### Discuss
26+
27+
If you have a question, check StackOverflow using
28+
[this list of tags](https://spring.io/questions), organized by Spring project.
29+
Find an existing discussion or start a new one if necessary.
30+
31+
If you suspect an issue, perform a search in the
32+
[Github issue tracker](https://github.com/spring-projects/spring-framework/issues), using a few different keywords.
33+
When you find related issues and discussions, prior or current, it helps you to learn and
34+
it helps us to make a decision.
35+
36+
#### Create a Ticket
37+
38+
Reporting an issue or making a feature request is a great way to contribute. Your feedback
39+
and the conversations that result from it provide a continuous flow of ideas.
40+
41+
Before you create a ticket, please take the time to [research first](#discuss).
42+
43+
If creating a ticket after a discussion on StackOverflow, please provide a self-sufficient description in the ticket, independent of the details on StackOverview. We understand this is extra work but the issue tracker is an important place of record for design discussions and decisions that can often be referenced long after the fix version, for example to revisit decisions, to understand the origin of a feature, and so on.
44+
45+
When ready create a ticket in the [Github issue tracker](https://github.com/spring-projects/spring-framework/issues).
46+
47+
#### Ticket Lifecycle
48+
49+
When an issue is first created, it may not be assigned and will not have a fix version.
50+
Within a day or two, the issue is assigned to a specific committer and the target
51+
version is set to "Waiting for Triage". The committer will then review the issue, ask for
52+
further information if needed, and based on the findings, the issue is either assigned a fix
53+
version or rejected.
54+
55+
When a fix is ready, the issue is marked "Resolved" and may still be re-opened. Once a fix
56+
is released, the issue is permanently "Closed". If necessary, you will need to create a new,
57+
related ticket with a fresh description.
58+
59+
#### Submit a Pull Request
60+
61+
You can contribute a source code change by submitting a pull request.
62+
63+
1. If you have not previously done so, please sign the
64+
[Contributor License Agreement](https://cla.pivotal.io/sign/spring). You will also be reminded
65+
automatically when you submit a pull request.
66+
67+
1. For all but the most trivial of contributions, please [create a ticket](#create-a-ticket).
68+
The purpose of the ticket is to understand and discuss the underlying issue or feature.
69+
We use the GitHub issue tracker as the preferred place of record for conversations and
70+
conclusions. In that sense discussions directly under a PR are more implementation detail
71+
oriented and transient in nature.
72+
73+
1. Always check out the `master` branch and submit pull requests against it
74+
(for target version see [settings.gradle](settings.gradle)).
75+
Backports to prior versions will be considered on a case-by-case basis and reflected as
76+
the fix version in the issue tracker.
77+
78+
1. Use short branch names, preferably based on the GitHub issue (e.g. `22276`), or
79+
otherwise using succinct, lower-case, dash (-) delimited names, such as `fix-warnings`.
80+
81+
1. Choose the granularity of your commits consciously and squash commits that represent
82+
multiple edits or corrections of the same logical change. See
83+
[Rewriting History section of Pro Git](https://git-scm.com/book/en/Git-Tools-Rewriting-History)
84+
for an overview of streamlining commit history.
85+
86+
1. Format commit messages using 55 characters for the subject line, 72 lines for the
87+
description, followed by the issue fixed, e.g. `Fixes #22276`.
88+
See the
89+
[Commit Guidelines section of Pro Git](https://git-scm.com/book/en/Distributed-Git-Contributing-to-a-Project#Commit-Guidelines)
90+
for best practices around commit messages and use `git log` to see some examples.
91+
92+
1. List the GitHub issue number in the PR description.
93+
94+
If accepted, your contribution may be heavily modified as needed prior to merging.
95+
You will likely retain author attribution for your Git commits granted that the bulk of
96+
your changes remain intact. You may also be asked to rework the submission.
97+
98+
If asked to make corrections, simply push the changes against the same branch, and your
99+
pull request will be updated. In other words, you do not need to create a new pull request
100+
when asked to make changes.
101+
102+
### Build from Source
103+
104+
See the [Build from Source](https://github.com/spring-projects/spring-framework/wiki/Build-from-Source)
105+
wiki page for instructions on how to check out, build, and import the Spring Framework
106+
source code into your IDE.
107+
108+
### Source Code Style
109+
110+
The wiki pages
111+
[Code Style](https://github.com/spring-projects/spring-framework/wiki/Code-Style) and
112+
[IntelliJ IDEA Editor Settings](https://github.com/spring-projects/spring-framework/wiki/IntelliJ-IDEA-Editor-Settings)
113+
defines the source file coding standards we use along with some IDEA editor settings we customize.
114+
115+
### Reference Docs
116+
117+
The reference documentation is in the [src/docs/asciidoc](src/docs/asciidoc) directory and, in
118+
[Asciidoctor](https://asciidoctor.org/) format. For trivial changes, you may be able to browse,
119+
edit source files, and submit directly from GitHub.
120+
121+
When making changes locally, use `./gradlew asciidoctor` and then browse the result under
122+
`build/asciidoc/html5/index.html`.
123+
124+
Asciidoctor also supports live editing. For more details read
125+
[Editing AsciiDoc with Live Preview](https://asciidoctor.org/docs/editing-asciidoc-with-live-preview/).
126+
Note that if you choose the
127+
[System Monitor](https://asciidoctor.org/docs/editing-asciidoc-with-live-preview/#using-a-system-monitor)
128+
option, you can find a Guardfile under `src/docs/asciidoc`.

‎README.md‎

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
# <img src="src/docs/asciidoc/images/spring-framework.png" width="80" height="80"> Spring Framework
2+
3+
This is the home of the Spring Framework: the foundation for all [Spring projects](https://spring.io/projects). Collectively the Spring Framework and the family of Spring projects is often referred to simply as "Spring".
4+
5+
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](https://docs.spring.io/spring/docs/current/spring-framework-reference/overview.html#spring-introduction) section as reference for a more complete introduction.
6+
7+
## Code of Conduct
8+
9+
This project is governed by the [Spring Code of Conduct](CODE_OF_CONDUCT.adoc). By participating, you are expected to uphold this code of conduct. Please report unacceptable behavior to [email protected].
10+
11+
## Access to Binaries
12+
13+
For access to artifacts or a distribution zip, see the [Spring Framework Artifacts](https://github.com/spring-projects/spring-framework/wiki/Spring-Framework-Artifacts) wiki page.
14+
15+
## Documentation
16+
17+
The Spring Framework maintains reference documentation ([published](https://docs.spring.io/spring-framework/docs/current/spring-framework-reference/) and [source](src/docs/asciidoc)), Github [wiki pages](https://github.com/spring-projects/spring-framework/wiki), and an
18+
[API reference](https://docs.spring.io/spring-framework/docs/current/javadoc-api/). There are also [guides and tutorials](https://spring.io/guides) across Spring projects.
19+
20+
## Build from Source
21+
22+
See the [Build from Source](https://github.com/spring-projects/spring-framework/wiki/Build-from-Source) Wikipedia page and the [CONTRIBUTING.md](CONTRIBUTING.md) file.
23+
24+
## Stay in Touch
25+
26+
Follow [@SpringCentral](https://twitter.com/springcentral), [@SpringFramework](https://twitter.com/springframework), and its [team members](https://twitter.com/springframework/lists/team/members) on Twitter. In-depth articles can be found at [The Spring Blog](https://spring.io/blog/), and releases are announced via our [news feed](https://spring.io/blog/category/news).
27+
28+
## License
29+
30+
The Spring Framework is released under version 2.0 of the [Apache License](https://www.apache.org/licenses/LICENSE-2.0).
31+
32+
版本：5.1
33+
中文注释

0 commit comments

Comments
 (0)