Changes requiring schema generation are exceedingly rare; favor
manual execution of `gradle generateSql` for the time being.
Generated sources are checked into the tree at
src/main/resources/org/springframework/integration; simply regenerate
and copy to this location manually as necessary.
This was due to Gradle's silent failure to match exclusions detailed
at http://jira.codehaus.org/browse/GRADLE-1028. Everything is working
as expected now after this update, however.
Requires significant pom customization in maven-deployment.gradle
which has been verified at `gradle install` time, but not yet at
`gradle uploadArchives` time. Need to figure out how to eliminate
the duplication going on there.
Before (Maven): http://pastie.org/1253428
After (Gradle): http://pastie.org/1253435
This new task:
- may be run independently with `gradle generateSql`
- is tied to the build lifecycle and will execute prior to 'compileJava'
- writes output to build/generated-resources
- is set up for incremental build -- will not run if the above dir exists
- may be selectively cleaned with `gradle cleanGenerateSql`
Complete:
--------
- src/* documentation resources moved to 'docs' subproject
- docbook sources upgraded to Docbook 5
- formatted all docbook sources to strip tab characters and
eliminate trailing whitespace
- all projects compile and test successfully
- all artifacts upload successfully to s3, static.sf.org, etc.
Remaining:
---------
- documentation L&F needs work. CSS, images, and highlighting aren't
hooked up properly
- spring-integration-jdbc codegen bits in Maven POM need to be
transcribed into gradle
- dependencies that were optional or provided scope in maven are
currently 'compile' scope in Gradle. Need to figure out support
in Gradle to fix this.
- run through Eclipse classpath and project generation scenarios
- delete all Maven artifacts
