spring-framework

Spring Framework

Chris Beams d7d1b495f2 Polish "Support flash attrs..." and related classes - 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.		14 years ago
..
.settings	ModelAndViewContainer related refinements	15 years ago
src	Polish "Support flash attrs..." and related classes	14 years ago
.classpath	[SPR-8222] Upgraded to JUnit 4.9.	15 years ago
.project	adding eclipse project meta-data, .classpath file is based on dependencies listed in ivy.xml	18 years ago
build.xml	+ upgrade to AspectJ 1.6.8	16 years ago
ivy.xml	shortened build properties "org.junit.version" to "junit.version" and "org.testng.version" to "testng.version"; reverted SLF4J version back to 1.5.3 (for Hibernate 3.3.1 compatibility)	15 years ago
pom.xml	Increment version to 3.1.1.BUILD-SNAPSHOT	14 years ago
template.mf	marked Apache HttpComponents dependency as optional (SPR-8788); cleanup of conversation dependencies	15 years ago
web.iml	updated IntelliJ dependency descriptors	15 years ago