This change publishes a build scan to ge.spring.io for every local build from an authenticated Spring committer and for CI where appropriate access tokens are available. The build will not fail if publishing fails.
This change also allows the build to benefit from local and remote build caching, providing faster builds for all contributors.
Additionally, the project will have access to all features of Gradle Enterprise such as:
- Dashboards to view all historical build scans, along with performance
trends over time
- Build failure analytics for enhanced investigation and diagnosis of
build failures
- Test failure analytics to better understand trends and causes around
slow, failing, and flaky tests
Resolves#1376.
The Spring WS BOM itself uses the flatten-maven-plugin to produce a POM file simplified for community consumption. The same plugin is ready to go for the other modules. But given the risk of breaking existing users, it will not be applied until Spring WS 4.1 is released (#1307).
Resolves#1290.
Related: #1205, #1285.
Only apply the Eclipse plugin to subprojects. This prevents the
creation of an Eclipse project for the root Gradle project which was
masking the Eclipse projects for all of the Gradle sub-projects.
Update .gitignore to ignore the bin folder created by builds in
Eclipse.
This commit migrates from a Maven-based build system to a Gradle-based
one. Changes include:
- Removed archetype & parent
- Renamed core, support, test, security and xml directories to
spring-ws-core, spring-ws-test, spring-ws-security, spring-xml
respectively.
- Moved samples to separate project
(https://github.com/spring-projects/spring-ws-samples)
