Steven van Beelen

Be sure to check out [this](https://github.com/AxonFramework/AxonFramework/commit/3699de8260fd49cea04c49f96ed86d7eba460a9e#commitcomment-155490506) comment thread with @timtebeek when picking up this issue.

Moved issue from 5.0.1 to 5.1.0. After the initial implementation in PR #3964, we had a debate of the usage of this component. Especially having noted the deadlock, we don't...

Added this issue to milestone 5.3.0 and gave it a low priority. I am assuming we will no longer do milestone/release candidates once 5.0.0 is out the door. However, as...

I agree that `EventTag` should support meta-annotations. So thanks for that. > Previously it supported repeatable for the same field but now it doesn't - I don't personally see any...

> annotation utils don't support repeatable right now, fyi Yes, noted! That's something it should support for this case I think. Or, that seems like the right angle to take...

Similarly as with #3704, thanks a ton for the investigation here. Given the fact we're making Axon Framework 5 "Async Native", there may be a window this scenario will come...

> [@smcvb](https://github.com/smcvb) should I mark `ConnectionProvider` as internal for now then as this change may require interface changes/replacements? Yes please!

Adding the status "blocked" to this issue, as work can only start here once [#3952](https://github.com/AxonFramework/AxonFramework/issues/3952) has been resolved. Moreover, there's a chance **this** issue will be resolved entirely as a...

This should be taken care of automatically as part of #3559. As #3559 is slated for 5.3.0, I am adding this bug to 5.3.0.

Moving issue to 4.12.1 as 4.12.0 will be released soon. We aim to resolve this issue around the time we release Axon Framework 5. Cannot deprecate code without a clear...