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 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
- Switch propdeps-plugin to custom OptionalDependenciesPlugin
- Switch io.spring.dependency-management with custom
spring-statemachine-platform project
- Use proper gradle publication system
- Switch to testfixtures from a custom tests jar
- Migrate to spring-asciidoctor-backends
- Generic changes to bom/starter create as we now use publications
- When going from boot 2.4.x to 2.5.x build didn't get
fatjar anymore, instead only "plain" jar were published.
- This same thing happened with local install and
artifactory publish.
- Define bootJar as artifact in sample projects.
- Fixes#994
- Restore all regions of statemachine
- A persisted statemachine with orthogonal states will not be correctly
restored as only the top region gets correctly reset. Tests in
StateMachineResetTests use the correct way to reset the statemachine
with all regions
- Fixes#978
- testing: added test case for dynamic generated id
- docs: update documentation
- fix: Support @WithStateMachine for machines generated using either empty id or dynamically generated id
- Fixes#940
