spring-framework

Spring Framework

Phillip Webb ad543dbee3 Use mapped annotation values when resolving mirrors Update `TypeMappedAnnotation` mirror resolution logic so that mapped annotation values are also considered. Prior to this commit, mirrors in more complex meta-annotation scenarios would not resolve correctly. Specifically, given the following: @interface TestAliased { @AliasFor(attribute = "qualifier") String value() default ""; @AliasFor(attribute = "value") String qualifier() default ""; } @TestAliased @interface TestMetaAliased { @AliasFor(annotation = Aliased.class, attribute = "value") String value() default ""; } @TestMetaAliased("test") @interface TestComposed { } A merged `@TestAliased` annotation obtained from a `@TestComposed` root annotation would return a `value` and `qualifier` of "". This was because the "value" and "qualifier" mirrors needed to be resolved against the `@TestMetaAliased` meta-annotation. They cannot be resolved against the declared `@TestComposed` annotation because it does not have any attributes. Our previous tests only covered a single depth scenario where `@TestMetaAliased` was used directly on the annotated element. Closes gh-23767 Co-authored-by: Sam Brannen <sbrannen@pivotal.io>		6 years ago
..
kotlin-coroutines	Upgrade to Coroutines 1.3.2	6 years ago
src	Use mapped annotation values when resolving mirrors	6 years ago
spring-core.gradle	Use dependency management in Framework build	6 years ago