spring-framework

Spring Framework

Chris Beams bf541db5b0 Refactor to consistent use of AnnotationAttributes Uses of AnnotationMetadata#getAnnotationAttributes throughout the framework have been updated to use the new AnnotationAttributes API in order to take advantage of the more concise, expressive and type-safe methods there. All changes are binary compatible to the 3.1.0 public API, save the exception below. A minor binary compatibility issue has been introduced in AbstractCachingConfiguration, AbstractAsyncConfiguration and AbstractTransactionManagementConfiguration when updating their protected Map<String, Object> fields representing annotation attributes to use the new AnnotationAttributes API. This is a negligible breakage, however, as the likelilhood of users subclassing these types is very low, the classes have only been in existence for a short time (further reducing the likelihood), and it is a source-compatible change given that AnnotationAttributes is assignable to Map<String, Object>.		14 years ago
..
.settings	Merge 3.1.0 development branch into trunk	16 years ago
src	Refactor to consistent use of AnnotationAttributes	14 years ago
.classpath	Upgrade to Hibernate Validator 4.2.0.Final	14 years ago
.project	Convert CRLF=>LF on files missed earlier	14 years ago
.springBeans	Remove "Feature" support introduced in 3.1 M1	15 years ago
build.xml	+ upgrade to AspectJ 1.6.8	16 years ago
context.iml	Convert CRLF=>LF on files missed earlier	14 years ago
ivy.xml	used specific SLF4J versions for running the test suites of individual modules (fixing the Hibernate Validator 4.2 upgrade)	14 years ago
pom.xml	Add <license> section to 3.1.x Maven poms	14 years ago
template.mf	cleanup of conversation dependencies	15 years ago