Page Comparison

...

버전	날짜	참고
1.0	2004년 3월	https://spring.io/blog/2004/03/24/spring-framework-1-0-final-released
2.0	2006년 10월	https://spring.io/blog/2006/10/03/spring-2-0-final-released
2.5	2007년 11월	https://spring.io/blog/2007/11/19/spring-framework-2-5-released
3.0	2009년 12월	https://spring.io/blog/2009/12/16/spring-3-0-0-is-now-available
3.1	2011년 12월	https://spring.io/blog/2011/12/13/spring-framework-3-1-goes-ga/
3.2	2012년 12월	https://spring.io/blog/2012/12/13/spring-framework-3-2-goes-ga/
4.0	2013년 12월	https://spring.io/blog/2013/12/12/announcing-spring-framework-4-0-ga-release
4.1	2014년 9월	https://spring.io/blog/2014/09/04/spring-framework-4-1-ga-is-here
4.2	2015년 7월	https://spring.io/blog/2015/07/31/spring-framework-4-2-goes-ga

목표

Note

title	주의사항

J2EE should be easier to use.
It's best to program to interfaces, rather than classes. Spring reduces the complexity cost of using interfaces to zero.
JavaBeans offer a great way of configuring applications.
OO design is more important than any implementation technology, such as J2EE.
Checked exceptions are overused in Java. A framework shouldn't force you to catch exceptions you're unlikely to be able to recover from.
Testability is essential, and a framework such as Spring should help make your code easier to test.
Our philosophy is summarized in “Expert One-on-One J2EE Design and Development” by Rod Johnson.

Spring should be a pleasure to use.
Your application code should not depend on Spring APIs.
Spring should not compete with good existing solutions, but should foster integration. (For example, JDO, Toplink, and Hibernate are great O/R mapping solutions. We don't need to develop another one.)