Steven van Beelen

Hey @hjohn, just checking in to see whether you've had time to provide a gist for us and the team. No pressure, just trying to gauge the activity here.

Thanks for the detailed explanation, @hjohn. And, sad to hear you're not using Axon Framework at said project. Although unrelated to this issue, I'd be curious to hear the decision-making...

Added this issue to release 5.0.0 as we intend to validate the feasibility of this in the new APIs. Furthermore, this issue has been referenced in #1241, as it would...

Although awesome, I agree with your point to make this low priority (sadly enough, of course). To that end, I've marked it as a priority 4. Concerning the approach, I...

We do not envision having sufficient time to work on this before our intended release of 4.7.0. Hence, moving this issue to 4.8.0.

We do not envision having sufficient time to work on this before our intended release of 4.8.0. Added, we aim to direct our attention to the following major release. Due...

Thanks once more for filing an issue with us, @nils-christian! First and foremost, did this predicament start occurring with Axon Framework 4.7.1? Or did you face the same concern before...

> The issue is not exclusive to the 4.7.0 release but exists in 4.6.3 as well. Good to know. I assumed as much, but wanted to make sure. > Furthermore,...

Thanks so much for all the feedback here, @nils-christian. I have had some chats internally to discuss this occurrence on the `HandlerDefinition` and `HandlerEnhancerDefinition`. Both are acted on during the...

Added this issue to release 5.0.0 as with all the new APIs coming out, we need to have milestone releases and release candidates anyhow. Setting up an easier (GitHub?) workflow...