spring-framework/org.springframework.context
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>.
2012-02-07 21:57:49 +01:00
..
.settings Merge 3.1.0 development branch into trunk 2010-10-25 19:48:20 +00:00
src Refactor to consistent use of AnnotationAttributes 2012-02-07 21:57:49 +01:00
.classpath Upgrade to Hibernate Validator 4.2.0.Final 2011-12-09 13:09:11 +00:00
.project Convert CRLF=>LF on files missed earlier 2011-12-22 14:06:44 +01:00
.springBeans Remove "Feature" support introduced in 3.1 M1 2011-05-06 19:03:52 +00:00
build.xml + upgrade to AspectJ 1.6.8 2010-02-04 11:46:21 +00:00
context.iml Convert CRLF=>LF on files missed earlier 2011-12-22 14:06:44 +01:00
ivy.xml used specific SLF4J versions for running the test suites of individual modules (fixing the Hibernate Validator 4.2 upgrade) 2011-12-09 17:53:29 +00:00
pom.xml Add <license> section to 3.1.x Maven poms 2012-01-31 15:18:05 +01:00
template.mf cleanup of conversation dependencies 2011-10-20 09:56:07 +00:00