Loïc Mathieu

Another way would be to let Micronaut close queues when closing the application context using bean lifecycle (which handle beans dependencies so should be safe).

We can do both by providing adding `@PreDestroy` on the close method. The important point is that we need to remove all direct calls to close, except on test.

@brian-mulier-p can we condidere that this has been done with the new way we close our server component with the changes done in 0.16 by @fhussonnois ?

Note that `@JsonInclude(JsonInclude.Include.NON_DEFAULT)` is still present in the following classes otherwise, task defaults will not work properly: `Task`, `Input`, `AbstractTrigger`. To be coherent I also added the annotation to the...

@anna-geller some description for the BC ### Change in the way we serialize JSON objects We previously serialized JSON objects with a `NON_DEFAULT` strategy; this means that only the properties...

@Skraye when you didn't find any test ... the best is to add one.

It misses a description of what it fixes and a test.

In the integration world (EAI/ESB/SOA) we refere at this by the name of correlation identifier (correlationId) as it allows to correlate multiple messages (here executions) together.

If we do this we may take the opportunity to move core tasks to a dedicated module and create a real plugin for them.

We propose to move all core task/triggers/conditions to a package `io.kestra.plugin.core`. While doing this, we want to take the opportunity to move the core plugin out of the `core` library,...