Juergen Hoeller 2564db2bfd LoadTimeWeaverAware beans are consistently being created early for JPA weaving to work reliably ...

Includes a change for factory methods that declare their return type as FactoryBean: When asked for a specific type match (e.g. LoadTimeWeaverAware), we do check early singleton instances as well (reusing the instances that we create for getObjectType checks). This is necessary in order to make @Bean method introspection as capable as XML bean definition introspection, even in case of the @Bean method using a generic FactoryBean declaration for its return type (instead of the FactoryBean impl class).

Issue: SPR-9857

2012-10-12 17:13:07 +02:00

..

.settings

Merge 3.1.0 development branch into trunk

2010-10-25 19:48:20 +00:00

src

LoadTimeWeaverAware beans are consistently being created early for JPA weaving to work reliably

2012-10-12 17:13:07 +02:00

.classpath

Upgrade to Hibernate Validator 4.2.0.Final

2011-12-09 13:09:11 +00:00

.project

Add hamcrest to spring-aspects Eclipse classpath

2012-07-06 15:52:00 +02: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

Increment version to 3.1.3.BUILD-SNAPSHOT

2012-07-07 20:05:06 +02:00

template.mf

fixed OSGi metadata for optional "javax.inject" package import (SPR-9173)

2012-03-14 16:03:49 +01:00