root
/
spring-framework
mirror of https://github.com/spring-projects/spring-framework.git
1
0
Fork 0
Code Issues Actions 6 Packages Projects Releases Wiki Activity
spring-framework/spring-oxm/spring-oxm.gradle

98 lines
2.8 KiB
Groovy
Raw Normal View History

Move modules to independent build files The main `build.gradle` file contains now only the common build infrastructure; all module-specific build configurations have been moved to their own build file. Issue: SPR-15885
2017-08-21 20:41:55 +08:00
description = "Spring Object/XML Marshalling"
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).
2012-01-18 01:22:24 +08:00
configurations {
Polish .gradle file formatting to use tabs Replace spaces with tabs for consistency with Java source code
2012-12-07 04:56:24 +08:00
jibx
Polishing
2017-09-27 07:34:11 +08:00
xjc
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).
2012-01-18 01:22:24 +08:00
}
Correct reference to XJC classpath
2017-01-17 21:00:15 +08:00
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).
2012-01-18 01:22:24 +08:00
dependencies {
Upgrade to EclipseLink 2.7.6 and JiBX 1.3.3
2020-02-06 01:21:03 +08:00
jibx "org.jibx:jibx-bind:1.3.3"
Upgrade JiBX (and BCEL) towards support of 1.8 bytecode level This commit also drops the now-unused CUSTOM_COMPILATION test group and the outdated JavaVersion class. Issue: SPR-10423
2016-07-25 20:10:46 +08:00
jibx "org.apache.bcel:bcel:6.0"
Upgrade to JAXB 2.3.1, Groovy 2.5.4, Jetty 9.4.14, Tomcat 9.0.13 Includes JAX-WS 2.3.1, Awaitility 3.1.3, OkHttp 3.12, Woodstox 5.2.
2018-11-19 19:41:26 +08:00
xjc "javax.xml.bind:jaxb-api:2.3.1"
Consistently use double quotes (even if no interpolation needed) Includes upgrade to Hibernate ORM 5.3.5, EclipseLink 2.7.3, Selenium HtmlUnit Driver 2.32.1, Jetty 9.4.12 RC2.
2018-08-16 21:32:44 +08:00
xjc "com.sun.xml.bind:jaxb-core:2.3.0.1"
xjc "com.sun.xml.bind:jaxb-impl:2.3.0.1"
Upgrade to JAXB 2.3.1, Groovy 2.5.4, Jetty 9.4.14, Tomcat 9.0.13 Includes JAX-WS 2.3.1, Awaitility 3.1.3, OkHttp 3.12, Woodstox 5.2.
2018-11-19 19:41:26 +08:00
xjc "com.sun.xml.bind:jaxb-xjc:2.3.1"
Consistently use double quotes (even if no interpolation needed) Includes upgrade to Hibernate ORM 5.3.5, EclipseLink 2.7.3, Selenium HtmlUnit Driver 2.32.1, Jetty 9.4.12 RC2.
2018-08-16 21:32:44 +08:00
xjc "com.sun.activation:javax.activation:1.2.0"
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).
2012-01-18 01:22:24 +08:00
}
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
2012-04-14 17:37:55 +08:00
ext.genSourcesDir = "${buildDir}/generated-sources"
ext.flightSchema = "${projectDir}/src/test/resources/org/springframework/oxm/flight.xsd"
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).
2012-01-18 01:22:24 +08:00
task genJaxb {
Polish .gradle file formatting to use tabs Replace spaces with tabs for consistency with Java source code
2012-12-07 04:56:24 +08:00
ext.sourcesDir = "${genSourcesDir}/jaxb"
ext.classesDir = "${buildDir}/classes/jaxb"
Allow genJaxb's output to be cached when checkout locations differ Previously, the genJaxb task's input files were compared using absolute paths. This would result in a cache miss for two builds with identical files contents and different root directories. This commit updates the path sensitivity of the input to be relative to the build's root directory, thereby allowing caching to work irrespective of the source checkout location. Closes gh-23704
2019-09-25 22:44:01 +08:00
inputs.files(flightSchema).withPathSensitivity(PathSensitivity.RELATIVE)
Polish .gradle file formatting to use tabs Replace spaces with tabs for consistency with Java source code
2012-12-07 04:56:24 +08:00
outputs.dir classesDir
doLast() {
project.ant {
taskdef name: "xjc", classname: "com.sun.tools.xjc.XJCTask",
classpath: configurations.xjc.asPath
mkdir(dir: sourcesDir)
mkdir(dir: classesDir)
xjc(destdir: sourcesDir, schema: flightSchema,
package: "org.springframework.oxm.jaxb.test") {
produces(dir: sourcesDir, includes: "**/*.java")
}
Remove XMLBeans support Issue: SPR-13796
2016-07-05 05:29:29 +08:00
javac(destdir: classesDir, source: 1.8, target: 1.8, debug: true,
Polish .gradle file formatting to use tabs Replace spaces with tabs for consistency with Java source code
2012-12-07 04:56:24 +08:00
debugLevel: "lines,vars,source",
Correct reference to XJC classpath
2017-01-17 21:00:15 +08:00
classpath: configurations.xjc.asPath) {
Polish .gradle file formatting to use tabs Replace spaces with tabs for consistency with Java source code
2012-12-07 04:56:24 +08:00
src(path: sourcesDir)
include(name: "**/*.java")
include(name: "*.java")
}
copy(todir: classesDir) {
fileset(dir: sourcesDir, erroronmissingdir: false) {
exclude(name: "**/*.java")
}
}
}
}
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).
2012-01-18 01:22:24 +08:00
}
Move modules to independent build files The main `build.gradle` file contains now only the common build infrastructure; all module-specific build configurations have been moved to their own build file. Issue: SPR-15885
2017-08-21 20:41:55 +08:00
dependencies {
compile(project(":spring-beans"))
compile(project(":spring-core"))
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
optional("javax.xml.bind:jaxb-api")
optional("javax.activation:javax.activation-api")
optional("com.thoughtworks.xstream:xstream")
optional("org.jibx:jibx-run")
Move modules to independent build files The main `build.gradle` file contains now only the common build infrastructure; all module-specific build configurations have been moved to their own build file. Issue: SPR-15885
2017-08-21 20:41:55 +08:00
testCompile(project(":spring-context"))
Use Gradle test fixture support for spring-core See gh-23550
2019-12-28 18:44:40 +08:00
testCompile(testFixtures(project(":spring-core")))
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
testCompile("org.ogce:xpp3")
testCompile("org.codehaus.jettison:jettison") {
Consistently use double quotes (even if no interpolation needed) Includes upgrade to Hibernate ORM 5.3.5, EclipseLink 2.7.3, Selenium HtmlUnit Driver 2.32.1, Jetty 9.4.12 RC2.
2018-08-16 21:32:44 +08:00
exclude group: "stax", module: "stax-api"
Move modules to independent build files The main `build.gradle` file contains now only the common build infrastructure; all module-specific build configurations have been moved to their own build file. Issue: SPR-15885
2017-08-21 20:41:55 +08:00
}
testCompile(files(genJaxb.classesDir).builtBy(genJaxb))
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
testCompile("org.xmlunit:xmlunit-assertj")
testCompile("org.xmlunit:xmlunit-matchers")
testRuntime("com.sun.xml.bind:jaxb-core")
testRuntime("com.sun.xml.bind:jaxb-impl")
Fix Gradle warnings about task output As of Gradle 4.0, project SourceSets can have multiple output directories (one per programming language). This commit fixes warnings that are logged when a single output dir is considered by tasks. Issue: SPR-15885
2017-08-21 20:42:12 +08:00
}
Support alternate JDK versions in Gradle build This commit adds support for the following two JVM system properties that control the Gradle build for alternative JDKs (i.e., a JDK other than the one used to launch the Gradle process). - customJavaHome: absolute path to the alternate JDK installation to use to compile Java code and execute tests. Setting this system property causes Groovy 3.0 RC3 to be used instead of 2.5.x. This system property is also used in spring-oxm.gradle to determine whether JiBX is supported. - customJavaSourceVersion: Java version supplied to the `--release` command line flag to control the Java source and target compatibility version. Supported versions include 9 or higher. Do not set this system property if Java 8 should be used. Examples: ./gradlew -DcustomJavaHome=/opt/java/jdk-14 test ./gradlew --no-build-cache -DcustomJavaHome=/opt/java/jdk-14 test ./gradlew -DcustomJavaHome=/opt/java/jdk-14 -DcustomJavaSourceVersion=14 test See gh-24474
2020-02-05 22:11:59 +08:00
// JiBX compiler is currently not compatible with JDK 9+.
// If customJavaHome has been set, we assume the custom JDK version is 9+.
if ((JavaVersion.current() == JavaVersion.VERSION_1_8) && !System.getProperty("customJavaSourceVersion")) {
Fix Gradle warnings about task output As of Gradle 4.0, project SourceSets can have multiple output directories (one per programming language). This commit fixes warnings that are logged when a single output dir is considered by tasks. Issue: SPR-15885
2017-08-21 20:42:12 +08:00
compileTestJava {
def bindingXml = "${projectDir}/src/test/resources/org/springframework/oxm/jibx/binding.xml"
doLast() {
project.ant {
taskdef(name: "jibx",
classname: "org.jibx.binding.ant.CompileTask",
classpath: configurations.jibx.asPath)
Disable verbose JiBX logging in Gradle build
2019-03-31 19:26:38 +08:00
jibx(verbose: false, load: true, binding: bindingXml) {
Fix Gradle warnings about task output As of Gradle 4.0, project SourceSets can have multiple output directories (one per programming language). This commit fixes warnings that are logged when a single output dir is considered by tasks. Issue: SPR-15885
2017-08-21 20:42:12 +08:00
classpathset(dir: sourceSets.test.java.outputDir) {
include(name: "**/jibx/**/*")
}
}
}
}
}
Latest dependency updates (POI 3.17, Rome 1.8, EhCache 3.4, Caffeine 2.5.6, RxJava 2.1.4, Tomcat 8.5.21, JRuby 9.1.13, Rhino 1.7.7.2)
2017-09-23 17:28:19 +08:00
}