Releases: camunda-community-hub/micronaut-camunda-platform-7
Releases · camunda-community-hub/micronaut-camunda-platform-7
v0.15.0
Changes
- Telemetry data contains server name (Jetty, Tomcat, Undertow). Netty is not yet supported.
- Log duration when starting the process engine
- JobExecutor is disabled in tests. Please, use "execute(job())" to trigger the job executor
- Don't throw exception if Camunda version cannot be determined.
- Update to Micronaut 2.3.0
v0.14.0
Changes
- Changed HikariHP Connection defaults
- Transactions are rolled back even if the admin user creation is enabled
- Camunda version is logged on startup
- Update to Micronaut 2.2.3
v0.13.0
v0.12.0
Changes
- Admin user can be created automatically on start up
- The interfaces of the process engine and job executor customizers provide the integration project's specific implementations (Note: This is a breaking change)
v0.11.0
Changes
- Disable telemetry in tests automatically - configuration is not needed
- Add documentation how to write process tests
- Update to Micronaut 2.2.1
v0.10.1
Changes
- Telemetry counts the command executions and reports these (if telemetry is enabled)
v0.10.0
Changes
- Update to Micronaut 2.2.0
v0.9.0
Changes:
- Update to Camunda 7.14 - and allow telemetry to be configured
- Update to Micronaut 2.1.3
- Document handling of blocking operations
v0.8.0
Changes:
- Always use embedded process engine configuration (and remove standalone process engine configuration) for much better performance and developer experience (transaction handling).
- JobExecutor is configurable by replacing the DefaultJobExecutorCustomizer.
- Update to Micronaut 2.1.2
v0.7.0
Changes
- Service tasks: Classes referenced by package are now resolved from the application context if they are available
- The module micronaut-camunda-bpm-feature now includes the dependency org.camunda.bpm:camunda-engine which will be resolved transitively.
- Update to Micronaut 2.1.1