d7d1b495f2
- Eliminate trailing whitespace
- Update long method signatures to follow framework whitespace
conventions
Based on the following search,
$ git grep -A3 '^.public .* .*([^\{;]*$' */src/main
the strong convention throughout the framework when dealing with
methods having long signatures (i.e. many parameters) is to break
immediately after the opening paren, indent two tabs deeper and break
lines around 90 characters as necessary. Such signatures should also
be followed by a newline after the opening curly brace to break
things up visually.
The files edited in this commit had a particularly different style of
intenting arguments to align with each other vertically, but the
alignment only worked if one's tabstop is set at four spaces.
When viewed at a different tabstop value, the effect is is jarring,
both in that it is misaligned and significantly different from most
of the framework. The convention described above reads well at any
tabstop value.
|
||
|---|---|---|
| build-spring-framework | ||
| org.springframework.aop | ||
| org.springframework.asm | ||
| org.springframework.aspects | ||
| org.springframework.beans | ||
| org.springframework.context | ||
| org.springframework.context.support | ||
| org.springframework.core | ||
| org.springframework.expression | ||
| org.springframework.instrument | ||
| org.springframework.instrument.tomcat | ||
| org.springframework.integration-tests | ||
| org.springframework.jdbc | ||
| org.springframework.jms | ||
| org.springframework.orm | ||
| org.springframework.oxm | ||
| org.springframework.spring-library | ||
| org.springframework.spring-parent | ||
| org.springframework.test | ||
| org.springframework.transaction | ||
| org.springframework.web | ||
| org.springframework.web.portlet | ||
| org.springframework.web.servlet | ||
| org.springframework.web.struts | ||
| spring-build | ||
| spring-framework-reference | ||
| .gitignore | ||
| README.md | ||
| build.properties | ||
| build.versions | ||
| ci-build.properties | ||
| eclipse-code-formatter.xml | ||
| spring-framework.ipr | ||
| spring-framework.psf | ||
README.md
Spring Framework
The Spring Framework provides a comprehensive programming and configuration model for modern Java-based enterprise applications - on any kind of deployment platform. A key element of Spring is infrastructural support at the application level: Spring focuses on the "plumbing" of enterprise applications so that teams can focus on application-level business logic, without unnecessary ties to specific deployment environments.
The framework also serves as the foundation for Spring Integration, Spring Batch and the rest of the Spring family of projects. Browse the repositories under the SpringSource organization on GitHub for a full list.
.NET and Python variants are available as well.
Downloading artifacts
Instructions on downloading Spring artifacts via Maven and other build systems are available via the project wiki.
Documentation
See the current Javadoc and Reference docs.
Getting support
Check out the Spring forums and the Spring tag on StackOverflow. Commercial support is available too.
Issue Tracking
Spring's JIRA issue tracker can be found here. Think you've found a bug? Please consider submitting a reproduction project via the spring-framework-issues repository. The readme provides simple step-by-step instructions.
Building from source
Instructions on building Spring from source are available via the project wiki.
Contributing
Pull requests are welcome; you'll be asked to sign our contributor license agreement (CLA). Trivial changes like typo fixes are especially appreciated (just fork and edit!). For larger changes, please search through JIRA for similiar issues, creating a new one if necessary, and discuss your ideas with the Spring team.
Staying in touch
Follow @springframework and its team members on Twitter. In-depth articles can be found at the SpringSource team blog, and releases are announced via our news feed.
License
The Spring Framework is released under version 2.0 of the Apache License.