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

Reverted change for @Bean methods that declare FactoryBean as their return type: The effects of trying to create the FactoryBean to find out about its implementation type are too far-reaching. It's better to recommend declaring a specific return type in the method signature if you want the container to specifically react to your implementation type.

Issue: SPR-9857

2012-10-12 22:56:08 +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 22:56:08 +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