tchekai704/src-spring-framework - src-spring-framework - Gitea

Author	SHA1	Message	Date
Rob Winch	b255045541	Enable Jibx binding with TestGroup.CUSTOM_COMPILATION Previously the Jibx binding was commented out which caused failures when using the TestGroup.CUSTOM_COMPILATION Now the Jibx bindings are enabled when the CUSTOM_COMPILATION is enabled. Issue: SPR-10558	11 years ago
Juergen Hoeller	bb95a63eda	OpenJDK 8 build 99: Jibx compiler fails - ignoring Jibx tests for the time being	11 years ago
Chris Beams	830d73b4a7	Eliminate EBR dependencies and repository config Swap the following EBR-specific dependencies for their equivalents at Maven Central: - atinject-tck - jaxb - xmlbeans Remove the /ebr-maven-external repository from the build script entirely such that all dependencies are now resolved against a single repository: http://repo.springsource.org/libs-release	12 years ago
Phillip Webb	a268528726	Polish .gradle file formatting to use tabs Replace spaces with tabs for consistency with Java source code	12 years ago
Stevo Slavic	51ae6845ad	Fix JibxMarshallerTests failing on Windows Before this change JibxMarshallerTests would fail on Windows with an error message explaining that JiBX compiler generated classes are not found on the classpath for binding with name 'binding'. Tests would execute well on Linux and OS X. Actual root cause of this bug is found to be in JiBX 1.1.5 release that is used to build Spring. The binding name can be explicitly specified in JiBX binding file. If omitted, when generating classes the JiBX compiler as fall-back mechanism tries to derive the binding name from the binding file name. That logic had a bug which gets manifested when configured binding file path has mixed Windows and *nix style file separators, as in case of JibxMarshallerTests being executed on a Windows platform. This commit resolves this issue by upgrading Spring's build from JiBX 1.1.5 to 1.2.3, as the bug mentioned was fixed in JiBX 1.2. See JIBX-441 for more details. Issue: SPR-8360	13 years ago
Chris Beams	963b4e49a9	Upgrade to Gradle 1.0-rc1 - Fix deprecation warnings about dynamic properties; favor use of "extra properties extensions" per [1] - Certain such deprecations are still issued due to violations within the docbook-reference plugin. These will be fixed in an upcoming revision of the plugin, at which point spring-framework will upgrade to depend on it and these warnings will be eliminated [1] http://gradle.org/docs/current/dsl/org.gradle.api.plugins.ExtraPropertiesExtension.html Issue: SPR-9327	13 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	13 years ago
Chris Beams	d6712d5983	Generate spring-oxm test classes and bindings - Generate castor test classes with genCastor task - Generate xmlbeans test classes with genXmlbeans task - Generate JAXB2 test classes with genJaxb task - Generate JiBX bindings by extending existing compileTestJava task Test classes are written into their own dedicated output folders and tied into the spring-oxm classpath using the files(...).builtBy(...) directive. Incremental build works as expected across all of these customizations. `gradle eclipse` and `gradle idea` generate correct .project / .iml metadata respectively, i.e., these special cases do not cause a problem in the IDE (as they used to prior to the move to Gradle).	13 years ago