GitHub-Spring/spring-framework - spring-framework - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
Phillip Webb	d8a05592e2	Allow package private classes in spring.factories Update SpringFactoriesLoader so that package private classes can be used. Issue: SPR-13969	10 years ago
Stephane Nicoll	babbf6e871	Harmonize resources location Issue: SPR-12766	11 years ago
Arjen Poutsma	d6950d8add	StaxStreamXMLReader ignores significant whitespace The StaxStreamXMLReader no longer handles all whitespace as ignorable whitespace. Issue: SPR-12000	12 years ago
Arjen Poutsma	f2f355e76c	Improved StAX<->SAX bridge Improved the SAX to StAX (and vice-versa) bridge exposed via StaxUtils. The old integration had some issues with namespace declaration attributes, brought to light in a XMLUnit upgrade. Issue: SPR-11549	12 years ago
Stephane Nicoll	4cd818b9e4	Harmonize log configuration Prior to this commit, the codebase was using a mix of log4j.xml and log4j.properties for test-related logging configuration. This can be an issue as log4j takes the xml variant first when looking for a default bootstrap configuration. In practice, some modules declaring the properties variant were taking the xml variant configuration from another module. The general structure of the configuration has also been harmonized to provide a standard console output as well as an easy way to enable trace logs for the current module.	12 years ago
Arjen Poutsma	aeff91c1da	Moved SpringFactoriesLoader to io.support in order to resolve tangle.	14 years ago
Arjen Poutsma	988f376752	Added SpringFactoriesLoader	14 years ago
Sam Brannen	c461455c7c	Infer return type of parametrized factory methods Currently, if a factory method is parameterized and the corresponding variable types are declared on the method itself instead of on the enclosing class or interface, Spring always predicts the return type to be Object, even if the return type can be explicitly inferred from the method signature and supplied arguments (which are available in the bean definition). This commit introduces a new resolveParameterizedReturnType() method in GenericTypeResolver that attempts to infer the concrete type for the generic return type of a given parameterized method, falling back to the standard return type if necessary. Furthermore, AbstractAutowireCapableBeanFactory now delegates to resolveParameterizedReturnType() when predicting the return type for factory methods. resolveParameterizedReturnType() is capable of inferring the concrete type for return type T for method signatures similar to the following. Such methods may potentially be static. Also, the formal argument list for such methods is not limited to a single argument. - public <T> T foo(Class<T> clazz) - public <T> T foo(Object obj, Class<T> clazz) - public <V, T> T foo(V obj, Class<T> clazz) - public <T> T foo(T obj) Issue: SPR-9493	14 years ago
Chris Beams	02a4473c62	Rename modules {org.springframework.=>spring-} This renaming more intuitively expresses the relationship between subprojects and the JAR artifacts they produce. Tracking history across these renames is possible, but it requires use of the --follow flag to `git log`, for example $ git log spring-aop/src/main/java/org/springframework/aop/Advisor.java will show history up until the renaming event, where $ git log --follow spring-aop/src/main/java/org/springframework/aop/Advisor.java will show history for all changes to the file, before and after the renaming. See http://chrisbeams.com/git-diff-across-renamed-directories	14 years ago